git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 (Oct 2017, #06; Fri, 27)
Date: Sat, 28 Oct 2017 22:43:23 +0530	[thread overview]
Message-ID: <1509210803.2256.7.camel@gmail.com> (raw)
In-Reply-To: <xmqq7evhc7nw.fsf@gitster.mtv.corp.google.com>

On Fri, 2017-10-27 at 17:32 +0900, 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".
> 
>  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

  parent reply	other threads:[~2017-10-28 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  8:32 What's cooking in git.git (Oct 2017, #06; Fri, 27) Junio C Hamano
2017-10-27 18:50 ` Stefan Beller
2017-11-07  2:00   ` sb/submodule-recursive-checkout-detach-head Junio C Hamano
2017-11-07 17:05     ` sb/submodule-recursive-checkout-detach-head Stefan Beller
2017-11-08  0:21       ` sb/submodule-recursive-checkout-detach-head Junio C Hamano
2017-10-28 17:13 ` Kaartic Sivaraam [this message]
2017-10-29 13:13 ` What's cooking in git.git (Oct 2017, #06; Fri, 27) Johannes Schindelin
2017-10-29 14:18   ` Junio C Hamano
2017-10-29 15:18     ` Johannes Schindelin
2017-10-30  1:27       ` 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=1509210803.2256.7.camel@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).