From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Sat, 28 Jan 2012 06:46:14 GMT
Subject: Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used
Message-ID: <4F2399B6.8020507@alum.mit.edu>
In-Reply-To: <7vr4ykybnl.fsf@alter.siamese.dyndns.org>

On 01/28/2012 12:21 AM, Junio C Hamano wrote:
> Mark Jason Dominus <mjd@plover.com> writes:
> 
>> This should work, but doesn't:
>>
>>         % git branch
>>         * master
>>         % git branch  --edit-description  blarf
>>         [Edit description and exit editor normally]
>>         % cat .git/BRANCH_DESCRIPTION 
>>         I like blarf
>>         # Please edit the description for the branch
>>         #   blarf
>>         # Lines starting with '#' will be stripped.
>>         % git branch -a
>>         * master
>>
>> Where is branch blarf?
> 
> You haven't created one in that sequence yet.
> 
> This is more of a documentation bug. 
> 
> As the SYNOPSIS section makes it clear, the '--edit-description' is a
> separate mode from showing (the first group), creating or repointing (the
> second), or renaming (the third).
> 
> After that you should be able to say "git branch blarf" and view its
> description.

Given this design, shouldn't "git branch --edit-description" fail if the
branch doesn't already exist?

Shouldn't it also resolve ambiguous reference names?

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/