Re: receive.denyCurrentBranch
- From
Theodore Tso <tytso@mit.edu>
- Date
- Feb 9, 2009, 05:06 UTC
- Message-ID
- <20090209050659.GA12655@mini-me.lan>
- In-Reply-To
- <76718490902081747s7a1ebe12yaf08665429a594c6@mail.gmail.com>
On Sun, Feb 08, 2009 at 08:47:26PM -0500, Jay Soffian wrote:
Show 11 quoted lines
> I agree that a detached HEAD is a bad idea. The closest parallel that > I can come up with for git would be for receive-pack to store incoming > changes into separate branch hierarchy, NOT for it to detach HEAD. A > toy-patch I played around with earlier allowed this on the non-bare > upstream repo: > > [receive] > prefix = refs/remotes/incoming > > Then a push to refs/heads/master was automatically stored as > refs/remotes/incoming/master instead.
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?
- Ted