From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2017, #04; Tue, 14)
Date: Tue, 14 Nov 2017 11:12:51 +0530 [thread overview]
Message-ID: <5fce2d3b-c8a9-765f-46e6-a2bebcac875e@gmail.com> (raw)
In-Reply-To: <xmqqo9o55xny.fsf@gitster.mtv.corp.google.com>
> * 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.
--
[1]:
https://public-inbox.org/git/20171102065407.25404-1-kaartic.sivaraam@gmail.com/
---
Kaartic
next prev parent reply other threads:[~2017-11-14 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 3:47 What's cooking in git.git (Nov 2017, #04; Tue, 14) Junio C Hamano
2017-11-14 5:42 ` Kaartic Sivaraam [this message]
2017-11-14 6:16 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fce2d3b-c8a9-765f-46e6-a2bebcac875e@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).