git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Guillaume Wenzek <guillaume.wenzek@gmail.com>
To: git@vger.kernel.org
Subject: BUG Report: git branch ignore --no-abbrev flag
Date: Wed, 8 Mar 2017 19:14:24 +0100	[thread overview]
Message-ID: <CAAvNd=ir1qNQVaKphdg51AfGnsNgTrfvW2L6cca3SHiZrWNgHA@mail.gmail.com> (raw)

Hi,
After updating to git 2.12.0 on Monday I noticed that the "git branch"
wasn't behaving as usual.
As of today `git branch -vv --no-abbrev` outputs short hashes instead
of long one (as requested by --no-abbrev)[1]

git branch -vv --no-abbrev
* (HEAD detached at 2.12.1)                        1c69bf2 Add
recap-release since previous release messages didn't go out.
  master                                           eb70249
[origin/master] Fix: support parsing "git://" remote URI to Github URL


Expected output:

git branch --vv --no-abbrev
* (HEAD detached at 2.12.1)
1c69bf24be6de096d801435378be85a936ab0f29 Add recap-release since
previous release messages didn't go out.
  master
eb70249e724f933255b4d8c7096092f2764942b4 [origin/master] Fix: support
parsing "git://" remote URI to Github URL

[1] https://git-scm.com/docs/git-branch#git-branch---no-abbrev

I don't have any relevant configuration set.

             reply	other threads:[~2017-03-08 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 18:14 Guillaume Wenzek [this message]
2017-03-08 18:33 ` BUG Report: git branch ignore --no-abbrev flag Junio C Hamano
2017-03-08 21:59   ` Junio C Hamano
2017-03-08 22:16     ` [PATCH] branch: honor --abbrev/--no-abbrev in --list mode Junio C Hamano
2017-03-09 13:25       ` Jakub Narębski
2017-03-10 16:45         ` Junio C Hamano
2017-03-09  9:44     ` BUG Report: git branch ignore --no-abbrev flag Guillaume Wenzek
2017-03-09 10:38       ` Jeff King

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAAvNd=ir1qNQVaKphdg51AfGnsNgTrfvW2L6cca3SHiZrWNgHA@mail.gmail.com' \
    --to=guillaume.wenzek@gmail.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).