Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:52:52

Mark Jason Dominus [off-list ref] 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.

Re: BUG 1.7.9: git branch fails to create new branch when --edit-description is used

From: Michael Haggerty <hidden>
Date: 2016-06-15 22:52:52

On 01/28/2012 12:21 AM, Junio C Hamano wrote:
Mark Jason Dominus [off-list ref] writes:
quoted
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/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help