Re: What's cooking in git.git (Oct 2017, #06; Fri, 27)
- From
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
- Date
- Oct 28, 2017, 17:13 UTC
- Message-ID
- <1509210803.2256.7.camel@gmail.com>
- In-Reply-To
- <xmqq7evhc7nw.fsf@gitster.mtv.corp.google.com>
On Fri, 2017-10-27 at 17:32 +0900, Junio C Hamano wrote:
Show 11 quoted lines
> * jc/branch-name-sanity (2017-10-14) 3 commits > (merged to 'next' on 2017-10-16 at 174646d1c3) > + branch: forbid refs/heads/HEAD > + branch: split validate_new_branchname() into two > + branch: streamline "attr_only" handling in validate_new_branchname() > "git branch" and "git checkout -b" are now forbidden from creating > a branch whose name is "HEAD". > > Will cook in 'next'. > >
Good thing this is still cooking in 'next'. I guess there's a bug as a consequence of this series (though that's just a guess and has not been confirmed by a bisection). See,
https://public-inbox.org/git/1509209933.2256.4.camel@gmail.com/T/#u
-- Kaartic