From: Jeff King <peff@peff.net>
Date: Sun, 29 Jan 2012 03:18:44 GMT
Subject: Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used
Message-ID: <20120129031843.GA1347@sigill.intra.peff.net>
In-Reply-To: <7vbopoxp5q.fsf@alter.siamese.dyndns.org>

On Fri, Jan 27, 2012 at 11:27:29PM -0800, Junio C Hamano wrote:

> > Given this design, shouldn't "git branch --edit-description" fail if the
> > branch doesn't already exist?
> 
> The only use scenario in the original design was to have a way to store
> the description given a branch name, and giving a description to a branch
> that does not yet exist is outside the scope of the design. So it all
> boils down to what is the most convenient and the simplest to explain.

How do we define "branch exists"? That the ref exists? What about a HEAD
that points to a branch-to-be-born?

Specifically, I am wondering whether this:

  $ git init
  $ git branch --edit-description

should work. Right now it edits the description for "master", even
though you haven't yet committed to it.

-Peff