Re: What's cooking in git.git (Nov 2017, #04; Tue, 14)

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 14, 2017, 06:16 UTC
Message-ID: <xmqq375h4c6d.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <5fce2d3b-c8a9-765f-46e6-a2bebcac875e@gmail.com>

Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:

Show 22 quoted lines

>> * jc/branch-name-sanity (2017-10-14) 3 commits
>>  - 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".
>>
>>  Reported to cause problems when renaming HEAD during a rebase.
>>  cf. <49563f7c-354e-334e-03a6-c3a40884b6d0@gmail.com>
>
>
> Just wanted to note this explicitly. As I'm not aware how the problem
> with above series is going to be resolved, I've decided to stall the
> v4 of my series that tries to improve error messages shown when
> renaming the branch[1] until this problem gets resolved. I'm doing
> this as this series and my series touch the same code
> paths. Furthermore, I based my v3 off of 'next' when this series was
> in there.
>
> I'm not sure if the resolution to the problem might introduce
> conflicts with my series. Hence the stall.

It is not like the original author of a series _owns_ the code; it is open source after all. So if you are inclined to, you are welcome to fix it up or rewrite it, if somebody else's series that is not actively being worked on needs updating before you can continue your work.