All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Jason Dominus <mjd@plover.com>
To: git@vger.kernel.org
Subject: BUG 1.7.9: git branch fails to create new branch when --edit-description is used
Date: Fri, 27 Jan 2012 16:52:45 -0500	[thread overview]
Message-ID: <2443.1327701165@plover.com> (raw)


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?

Creating the branch and editing the description afterwards works correctly:

        % git branch blarf
        % git branch  --edit-description  blarf
        % git branch -a
          blarf
        * master
        % cat .git/config 
        [core]
                repositoryformatversion = 0
                filemode = true
                bare = false
                logallrefupdates = true
        [branch "master"]
                description = I like pie\n
        [branch "blarf"]
                description = I like blarf\n


Mark Jason Dominus 	  			                 mjd@plover.com

             reply	other threads:[~2012-01-27 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 21:52 Mark Jason Dominus [this message]
2012-01-27 23:21 ` BUG 1.7.9: git branch fails to create new branch when --edit-description is used Junio C Hamano
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=2443.1327701165@plover.com \
    --to=mjd@plover.com \
    --cc=git@vger.kernel.org \
    /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.