From: Markus Heidelberg <markus.heidelberg@web.de>
To: git@vger.kernel.org
Subject: inconsistency with --abbrev=0
Date: Sun, 31 May 2009 17:48:00 +0200 [thread overview]
Message-ID: <200905311748.00782.markus.heidelberg@web.de> (raw)
The minimum (>=4) number of chars is shown by
git log|show|whatchanged --abbrev-commit --raw --abbrev=0
git rev-list --abbrev-commit --abbrev=0 HEAD
git show-ref --abbrev=0
and the various diff commands
All 40 are shown by
git branch -v --abbrev=0
git ls-files --stage --abbrev=0
git ls-tree --abbrev=0 HEAD
The latter group uses parse-options and doesn't set abbrev to 4 in this
case. This is needed for git-describe to omit the output of the commit.
What should --abbrev=0 behave like?
Markus
next reply other threads:[~2009-05-31 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 15:48 Markus Heidelberg [this message]
2009-05-31 17:46 ` inconsistency with --abbrev=0 Sverre Rabbelier
2009-06-01 10:36 ` Markus Heidelberg
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=200905311748.00782.markus.heidelberg@web.de \
--to=markus.heidelberg@web.de \
--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).