Re: failed to lock

From: Jay Soffian <jaysoffian@gmail.com>
Date: Apr 15, 2010, 19:13 UTC
Message-ID: <k2j76718491004151213xdb223ff8kd43f170eaf3a470a@mail.gmail.com>
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:

Show 14 quoted lines

> 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.