Re: receive.denyCurrentBranch

From

Jay Soffian <jaysoffian@gmail.com>

Date

Feb 9, 2009, 15:46 UTC

Message-ID

<76718490902090746x49e06f54sa409eacf1078ddca@mail.gmail.com>

In-Reply-To

<alpine.DEB.1.00.0902091204100.10279@pacific.mpi-cbg.de>

>
> On Mon, 9 Feb 2009, Theodore Tso wrote:
>>
>>
>> What happens when the next person pushes to the same remote repo, and
>> their refs/heads/master push is not a fast-forward merge of the
>> current refs/remotes/incoming/master?
>>
>> Do you lose the first user's push at that point?  Or do you refuse the
>> push?
>
> This is meant for non-bare repositories, right?  Repositories that do have
> reflogs...

Absolutely. It would be insane on a bare repository.

> P.S.: There _have_ been times when I would have liked an automatic
> PUSH_HEAD that is always temporary, such as FETCH_HEAD.  I _could_ imagine
> that this is something we could do (opt-in, of course): storing what was
> already pushed in a PUSH_HEAD, even if the refs could not be updated.

Oooh. Interesting idea.

j.