All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: [PATCH 03/11] Document git log --abbrev-commit, as a kind of pretty option
Date: Sat, 16 Jun 2007 21:03:39 +0200	[thread overview]
Message-ID: <11820206321696-git-send-email-jnareb@gmail.com> (raw)
In-Reply-To: <11820206272990-git-send-email-jnareb@gmail.com>

Documentation taken from paraphrased description of "--abbrev[=<n>]"
diff option, and from description of commit 5c51c985 introducing
this option.

Note that to change number of digits one must use "--abbrev=<n>",
which affects [also] diff output.

Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
 Documentation/pretty-options.txt |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/Documentation/pretty-options.txt b/Documentation/pretty-options.txt
index 6338def..746bc5b 100644
--- a/Documentation/pretty-options.txt
+++ b/Documentation/pretty-options.txt
@@ -5,6 +5,15 @@
 	'full', 'fuller', 'email', 'raw' and 'format:<string>'.
 	When left out the format default to 'medium'.
 
+--abbrev-commit::
+	Instead of showing the full 40-byte hexadecimal commit object
+	name, show only handful hexdigits prefix.  Non default number of
+	digits can be specified with "--abbrev=<n>" (which also modifies
+	diff output, if it is displayed).
++
+This should make "--pretty=oneline" a whole lot more readable for
+people using 80-column terminals.
+
 --encoding[=<encoding>]::
 	The commit objects record the encoding used for the log message
 	in their encoding header; this option can be used to tell the
-- 
1.5.2

  parent reply	other threads:[~2007-06-16 18:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 19:03 [PATCH 00/11] Document missing options Jakub Narebski
2007-06-16 19:03 ` [PATCH 01/11] Use tabs for indenting definition list for options in git-log.txt Jakub Narebski
2007-06-16 19:03 ` [PATCH 02/11] Document git log --full-diff Jakub Narebski
2007-06-16 19:03 ` Jakub Narebski [this message]
2007-06-16 19:03 ` [PATCH 04/11] Document that '--message=<msg>' is long version of '-m <msg>' Jakub Narebski
2007-06-16 19:03 ` [PATCH 05/11] Document that '--no-checkout' is long version of '-n' option of git-clone Jakub Narebski
2007-06-16 19:03 ` [PATCH 06/11] Document git rev-list --timestamp Jakub Narebski
2007-06-16 19:03 ` [PATCH 07/11] Document git rev-list --full-history Jakub Narebski
2007-06-16 19:03 ` [PATCH 08/11] Document git rev-parse --is-inside-git-dir Jakub Narebski
2007-06-16 19:03 ` [PATCH 09/11] Document git read-tree --trivial Jakub Narebski
2007-06-16 19:03 ` [PATCH 10/11] Document git reflog --stale-fix Jakub Narebski
2007-06-16 19:03 ` [PATCH 11/11] Document git commit --untracked-files and --verbose Jakub Narebski
2007-06-16 20:06   ` Junio C Hamano
2007-06-16 22:29     ` Jakub Narebski

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=11820206321696-git-send-email-jnareb@gmail.com \
    --to=jnareb@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.
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.