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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Junio,

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

> * 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



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux