All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Anatol Rudolph <a.rudolph@2vizcon.com>, git@vger.kernel.org
Subject: Re: git branch command is incompatible with bash
Date: Tue, 28 Jul 2015 08:23:40 -0700	[thread overview]
Message-ID: <xmqq4mkogvb7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <55B72F09.3030000@kdbg.org> (Johannes Sixt's message of "Tue, 28 Jul 2015 09:28:09 +0200")

Johannes Sixt <j6t@kdbg.org> writes:

> Are you trying to say that the result of 'rev-parse --abbrev-ref HEAD'
> is suboptimal and that of 'symbolic-ref --short HEAD' is OK?

My "Interesting" was primarily about that I wasn't aware of the
"--abbrev-ref" option.

Yes, I am sure some time ago I accepted a patch to add it, but I
simply do not see the point, especially because the "--short" option
to symbolic-ref feels much more superiour.  "What branch am I on?"
is about symbolic refs, rev-parse is about revisions.

I can see that "symbolic-ref --short" is much newer than the other
one, so addition of "--abbrev-ref" to "rev-parse" may have been a
mistake made while being desperate (i.e. not having a way to do so
with plumbing, we wanted "some" way to do so and chose poorly).

  parent reply	other threads:[~2015-07-28 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 12:12 git branch command is incompatible with bash Anatol Rudolph
2015-07-27 21:11 ` Johannes Sixt
2015-07-27 21:49   ` Junio C Hamano
2015-07-28  7:28     ` Johannes Sixt
2015-07-28 10:01       ` Jakub Narębski
2015-07-28 15:23       ` Junio C Hamano [this message]
2015-07-28 16:25         ` Jeff King
2015-07-28 17:27         ` Johannes Sixt
2015-07-29  0:23         ` Scott Schmit

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=xmqq4mkogvb7.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=a.rudolph@2vizcon.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.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.