From: "Shawn O. Pearce" <spearce@spearce•org>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: [RFC] git-remote
Date: Thu, 4 Jan 2007 22:17:15 -0500 [thread overview]
Message-ID: <20070105031715.GE14042@spearce.org> (raw)
In-Reply-To: <7vodpejhmt.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox•net> wrote:
> By the way, do you have comments on my counterproposal for
> lockfile fix?
Yea, see the email in that thread.
Sorry for the lag. I've been sidetracked by a new and fairly useless
(to me anyway) project that I have to put a lot of time into now.
Arrgh. At least I have a sound version control system to track
its source code in. :-)
--
Shawn.
next prev parent reply other threads:[~2007-01-05 3:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 21:40 [RFC] git-remote Junio C Hamano
2007-01-03 22:05 ` Jakub Narebski
2007-01-05 3:02 ` Shawn O. Pearce
2007-01-05 3:07 ` Junio C Hamano
2007-01-05 3:17 ` Shawn O. Pearce [this message]
2007-01-05 12:59 ` Santi Béjar
2007-01-05 13:53 ` Johannes Schindelin
2007-01-05 19:53 ` Santi Béjar
2007-01-05 21:08 ` Carl Worth
2007-01-06 1:59 ` Junio C Hamano
2007-01-08 22:52 ` Carl Worth
2007-01-09 4:28 ` J. Bruce Fields
2007-01-09 5:48 ` Junio C Hamano
2007-01-09 5:50 ` Junio C Hamano
2007-01-09 9:22 ` Andreas Ericsson
2007-01-10 18:13 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070105031715.GE14042@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox