Git development
 help / color / mirror / Atom feed
From: Michael <barra_cuda@katamail.com>
To: git@vger.kernel.org
Subject: [PATCH] Documentation: explain "--pretty"
Date: Mon, 7 Aug 2006 21:32:20 +0200	[thread overview]
Message-ID: <200608072132.21032.barra_cuda@katamail.com> (raw)
Message-ID: <20060807192731.257508@dial-up-mi-21.lombardiacom.it> (raw)

Signed-off-by: Michael <barra_cuda@katamail.com>
---
 Documentation/git-diff-tree.txt   |    4 ++--
 Documentation/git-log.txt         |    2 ++
 Documentation/git-rev-list.txt    |    4 +++-
 Documentation/git-show.txt        |    2 +-
 Documentation/git-whatchanged.txt |    2 +-
 5 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/Documentation/git-diff-tree.txt b/Documentation/git-diff-tree.txt
index f7e8ff2..11d4f48 100644
--- a/Documentation/git-diff-tree.txt
+++ b/Documentation/git-diff-tree.txt
@@ -73,9 +73,9 @@ separated with a single space are given.
 	This flag causes "git-diff-tree --stdin" to also show
 	the commit message before the differences.
 
---pretty[=(raw|medium|short)]::
+--pretty[=(raw|medium|short|full|oneline)]::
 	This is used to control "pretty printing" format of the
-	commit message.  Without "=<style>", it defaults to
+	commit message.  Without "=<format>", it defaults to
 	medium.
 
 --no-commit-id::
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index c9ffff7..cd46580 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -26,6 +26,8 @@ OPTIONS
 -------
 --pretty=<format>::
 	Controls the way the commit log is formatted.
+	<format> can be one of 'raw', 'medium', 'short', 'full',
+	and 'oneline'.  Without "=<format>", it defaults to medium.
 
 --max-count=<n>::
 	Limits the number of commits to show.
diff --git a/Documentation/git-rev-list.txt b/Documentation/git-rev-list.txt
index f60eacd..761891e 100644
--- a/Documentation/git-rev-list.txt
+++ b/Documentation/git-rev-list.txt
@@ -49,8 +49,10 @@ between the two operands.  The following
 
 OPTIONS
 -------
---pretty::
+--pretty=<format>::
 	Print the contents of the commit changesets in human-readable form.
+	<format> can be one of 'raw', 'medium', 'short', 'full',
+	and 'oneline'.  Without "=<format>", it defaults to medium.
 
 --header::
 	Print the contents of the commit in raw-format; each
diff --git a/Documentation/git-show.txt b/Documentation/git-show.txt
index 2b4df3f..58c64ff 100644
--- a/Documentation/git-show.txt
+++ b/Documentation/git-show.txt
@@ -29,7 +29,7 @@ OPTIONS
 --pretty=<format>::
 	Controls the output format for the commit logs.
 	<format> can be one of 'raw', 'medium', 'short', 'full',
-	and 'oneline'.
+	and 'oneline'.  Without "=<format>", it defaults to medium.
 
 Author
 ------
diff --git a/Documentation/git-whatchanged.txt 
b/Documentation/git-whatchanged.txt
index e8f21d0..4d7d45f 100644
--- a/Documentation/git-whatchanged.txt
+++ b/Documentation/git-whatchanged.txt
@@ -41,7 +41,7 @@ OPTIONS
 --pretty=<format>::
 	Controls the output format for the commit logs.
 	<format> can be one of 'raw', 'medium', 'short', 'full',
-	and 'oneline'.
+	and 'oneline'.  Without "=<format>", it defaults to medium.
 
 -m::
 	By default, differences for merge commits are not shown.
-- 
1.4.2.rc3

                 reply	other threads:[~2006-08-07 19:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200608072132.21032.barra_cuda@katamail.com \
    --to=barra_cuda@katamail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox