From: Namhyung Kim <namhyung@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH v2 3/3] Documentation: add --abbrev option to the man page of git blame
Date: Wed, 6 Apr 2011 11:20:52 +0900 [thread overview]
Message-ID: <1302056452-5387-3-git-send-email-namhyung@gmail.com> (raw)
In-Reply-To: <1302056452-5387-1-git-send-email-namhyung@gmail.com>
Signed-off-by: Namhyung Kim <namhyung@gmail.com>
---
Documentation/git-blame.txt | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-blame.txt b/Documentation/git-blame.txt
index c4d1ff8..27ce6bd 100644
--- a/Documentation/git-blame.txt
+++ b/Documentation/git-blame.txt
@@ -9,7 +9,7 @@ SYNOPSIS
--------
[verse]
'git blame' [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental] [-L n,m]
- [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>]
+ [-S <revs-file>] [-M] [-C] [-C] [-C] [--since=<date>] [--abbrev=<n>]
[<rev> | --contents <file> | --reverse <rev>] [--] <file>
DESCRIPTION
@@ -73,6 +73,12 @@ include::blame-options.txt[]
Ignore whitespace when comparing the parent's version and
the child's to find where the lines came from.
+--abbrev=<n>::
+ Instead of using the default 7+1 hexadecimal digits as the
+ abbreviated object name, use <n>+1 digits. Note that git
+ will add 1 for the boundary commit to be distinguished (with
+ a caret at the beginning).
+
THE PORCELAIN FORMAT
--------------------
--
1.7.4
next prev parent reply other threads:[~2011-04-06 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 2:20 [PATCH v2 1/3] blame: add --abbrev command line option Namhyung Kim
2011-04-06 2:20 ` [PATCH v2 2/3] blame: honor core.abbrev Namhyung Kim
2011-04-06 2:20 ` Namhyung Kim [this message]
2011-04-06 2:46 ` [PATCH v2 1/3] blame: add --abbrev command line option Thiago Farina
2011-04-06 3:18 ` Junio C Hamano
2011-04-06 11:06 ` Namhyung Kim
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=1302056452-5387-3-git-send-email-namhyung@gmail.com \
--to=namhyung@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 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 NNTP newsgroup(s).