Re: What's cooking in git.git (Oct 2017, #07; Mon, 30)

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Oct 30, 2017, 17:28 UTC
Message-ID: <alpine.DEB.2.21.1.1710301827000.6482@virtualbox>
In-Reply-To: <xmqqr2tl40pl.fsf@gitster.mtv.corp.google.com>

Hi Junio,

On Mon, 30 Oct 2017, Junio C Hamano wrote:

Show 8 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".

Question: should we respect core.ignoreCase and if it is true, compare
case-insensitively? Or should we just keep the comparison
case-sensitively, in preparation for a (hopefully near) refs backend that
does not inherit filesystems' case-insensitivity?

Ciao, Dscho