From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Mark Jason Dominus <mjd@plover.com>, git@vger.kernel.org
Subject: Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used
Date: Sat, 28 Jan 2012 07:46:14 +0100 [thread overview]
Message-ID: <4F2399B6.8020507@alum.mit.edu> (raw)
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/
next prev parent reply other threads:[~2012-01-28 6:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 21:52 BUG 1.7.9: git branch fails to create new branch when --edit-description is used Mark Jason Dominus
2012-01-27 23:21 ` Junio C Hamano
2012-01-28 6:46 ` Michael Haggerty [this message]
2012-01-28 7:27 ` Junio C Hamano
2012-01-29 3:18 ` Jeff King
2012-01-29 6:30 ` Michael Haggerty
2012-01-29 6:42 ` Junio C Hamano
2012-01-29 10:11 ` Michael Haggerty
2012-01-29 21:49 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F2399B6.8020507@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mjd@plover.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.