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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html