From: Nicolas Pitre <nico@cam.org>
To: Tony Lindgren <tony@atomide.com>
Cc: git@vger.kernel.org, Matthias Urlichs <smurf@smurf.noris.de>
Subject: Re: [SCRIPT] cg-rpush & locking
Date: Tue, 31 May 2005 19:16:09 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0505311914550.6500@localhost.localdomain> (raw)
In-Reply-To: <20050531190005.GE18723@atomide.com>
On Tue, 31 May 2005, Tony Lindgren wrote:
> Anybody have any better ideas for locking that also works with
> rsync?
Why do you need a lock at all?
Just update your HEAD reference last when you push and get it first when
you pull.
Nicolas
next prev parent reply other threads:[~2005-05-31 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 19:00 [SCRIPT] cg-rpush & locking Tony Lindgren
2005-05-31 23:16 ` Nicolas Pitre [this message]
2005-06-01 6:51 ` Thomas Glanzmann
2005-06-01 16:55 ` Tony Lindgren
2005-06-02 2:58 ` Linus Torvalds
2005-06-02 6:39 ` Daniel Barkalow
2005-06-02 7:14 ` Matthias Urlichs
2005-06-02 7:32 ` Tony Lindgren
2005-06-02 10:04 ` Matthias Urlichs
2005-06-02 14:50 ` Linus Torvalds
2005-06-02 17:54 ` Tony Lindgren
2005-06-02 19:12 ` Daniel Barkalow
2005-06-02 19:15 ` Dan Holmsand
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=Pine.LNX.4.63.0505311914550.6500@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=smurf@smurf.noris.de \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).