From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: failed to lock
Date: Thu, 15 Apr 2010 15:13:12 -0400 [thread overview]
Message-ID: <k2j76718491004151213xdb223ff8kd43f170eaf3a470a@mail.gmail.com> (raw)
In-Reply-To: <7vd3y0k0c6.fsf@alter.siamese.dyndns.org>
On Thu, Apr 15, 2010 at 3:00 PM, Junio C Hamano <gitster@pobox.com> wrote:
> I would rather think that "git push" should notice that */HEAD is a symref
> and refrain from pushing it. Stated more precisely,
>
> - It is perfectly fine to do this:
>
> $ git push there HEAD:somebranch
>
> - But it does not make sense to push a symref via
>
> [remote "there"]
> push = refs/*:refs/*
>
> to a bare repository that is used as a back-up mirror by including
> refs/HEAD:refs/HEAD in the result of wildcard expansion.
But nothing prevents the destination repo from having arbitrary
symrefs. And there is no way for the source to know which destination
refs may be symrefs and which are not.
So it seems safer to me that the destination should ignore duplicates
in the received list.
No?
j.
next prev parent reply other threads:[~2010-04-15 19:13 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 [this message]
2010-04-15 22:27 ` Junio C Hamano
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=k2j76718491004151213xdb223ff8kd43f170eaf3a470a@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).