From: Junio C Hamano <gitster@pobox.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: failed to lock
Date: Thu, 15 Apr 2010 15:27:26 -0700 [thread overview]
Message-ID: <7vbpdkic6p.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <k2j76718491004151213xdb223ff8kd43f170eaf3a470a@mail.gmail.com> (Jay Soffian's message of "Thu\, 15 Apr 2010 15\:13\:12 -0400")
Jay Soffian <jaysoffian@gmail.com> writes:
> So it seems safer to me that the destination should ignore duplicates
> in the received list.
We probably need it on both ends.
On the receiving end, it probably is a better idea to make verify_lock()
succeed if the ref has already been updated to the value we are going to
update with, as I suspect that the issue is not limited to receive-pack.
It needs some restructuring of lock/verify/commit primitives, though.
prev parent reply other threads:[~2010-04-15 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 20:49 failed to lock Jay Soffian
2010-04-14 21:02 ` Jay Soffian
2010-04-15 4:00 ` Jay Soffian
2010-04-15 19:00 ` Junio C Hamano
2010-04-15 19:13 ` Jay Soffian
2010-04-15 22:27 ` Junio C Hamano [this message]
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=7vbpdkic6p.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.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).