From: Junio C Hamano <gitster@pobox.com>
To: Mark Jason Dominus <mjd@plover.com>
Cc: git@vger.kernel.org
Subject: Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used
Date: Fri, 27 Jan 2012 15:21:34 -0800 [thread overview]
Message-ID: <7vr4ykybnl.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <2443.1327701165@plover.com> (Mark Jason Dominus's message of "Fri, 27 Jan 2012 16:52:45 -0500")
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.
next prev parent reply other threads:[~2012-01-27 23:21 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 [this message]
2012-01-28 6:46 ` Michael Haggerty
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=7vr4ykybnl.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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 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 NNTP newsgroup(s).