Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 30, 2009, 16:55 UTC
- Message-ID
- <alpine.DEB.1.00.0901301754110.3586@pacific.mpi-cbg.de>
- In-Reply-To
- <20090130163317.GB6963@sigill.intra.peff.net>
Hi,
On Fri, 30 Jan 2009, Jeff King wrote:
Show 14 quoted lines
> On Fri, Jan 30, 2009 at 02:24:57PM +0100, Johannes Schindelin wrote: > > > Let's reap all the opinions about this issue, and then I'll do the > > wrap-up patch. > > I thought what Junio said was very reasonable (improve the message and > give it some more time to work). > > But I honestly do not care that much either way. I probably would have > made the original patch default to "deny" if not for discussion > recommending to be conservative. On the other hand, I don't think we > have really given the "warning" approach enough time to see whether it > is working (and I don't necessarily disagree with your gut feeling that > it won't work; I am undecided, which leads me to want more data).
It is not working:
http://groups.google.com/group/msysgit/msg/55b1aa03fbbbefba?dmode=source
(I am simply assuming that the mentioned 1.6.1-preview has the warning, since denyCurrentBranch is in v1.6.1-rc1~59^2, and I am too short on time to check it in detail (which would mean finding a Windows machine and running a test)).
Ciao, Dscho