git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Documentation: document show -s

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 9, 2010, 17:12 UTC
Message-ID
<20101109171248.GG18960@burratino>
In-Reply-To
<4CD97399.4010704@gnatter.net>

Git's diff machinery has supported a -s (silence diff output) option as far back as v0.99~900 (Silent flag for show-diff, 2005-04-13), but the option is only advertised in an odd corner of the git diff-tree manual.

The main use is to retrieve basic metadata about a commit:
	git show -s rev

Explain this in the 'git log' manual and provide an example in the 'git show' examples section. This is kind of a cop-out, since it would be more useful to explain it in the 'git show' manual proper, which says:

	The command takes options applicable to the git
	diff-tree command to control how the changes the
	commit introduces are shown.
	This manual page describes only the most frequently
	used options.
Fixing that is a larger task for another day.
Reported-by: Will Hall <will@gnatter.net>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
Will Hall wrote:
> I know this should be obvious but I can't find *any* reference to
> this in git show --help
Thanks, good catch.
 Documentation/git-show.txt         |    4 ++++
 Documentation/rev-list-options.txt |    3 +++
 2 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-show.txt b/Documentation/git-show.txt
index 2049c60..f0a8a1a 100644
--- a/Documentation/git-show.txt
+++ b/Documentation/git-show.txt
@@ -54,6 +54,10 @@ git show v1.0.0::
 git show v1.0.0^\{tree\}::
 	Shows the tree pointed to by the tag `v1.0.0`.
 
+git show -s --format=%s v1.0.0^\{commit\}::
+	Shows the subject of the commit pointed to by the
+	tag `v1.0.0`.
+
 git show next~10:Documentation/README::
 	Shows the contents of the file `Documentation/README` as
 	they were current in the 10th last commit of the branch
diff --git a/Documentation/rev-list-options.txt b/Documentation/rev-list-options.txt
index 7a42567..1aaaf5a 100644
--- a/Documentation/rev-list-options.txt
+++ b/Documentation/rev-list-options.txt
@@ -146,6 +146,9 @@ options may be given. See linkgit:git-diff-files[1] for more options.
 -t::
 
 	Show the tree objects in the diff output. This implies '-r'.
+
+-s::
+	Suppress diff output.
 endif::git-rev-list[]
 
 Commit Limiting
-- 
1.7.2.3.557.gab647.dirty
Previous: Will HallNext: Matthieu Moy
Message 12 of 17 in “More consistant terminology”
  1. 00/10 More consistant terminologyMatthieu Moy, Nov 2, 2010
  2. 01/10 Better "Changed but not updated" message in git-statusMatthieu Moy, Nov 2, 2010
  3. 02/10 Replace "remote tracking" with "remote-tracking"Matthieu Moy, Nov 2, 2010
  4. 03/10 Change remote tracking to remote-tracking in non-trivial placesMatthieu Moy, Nov 2, 2010
  5. 04/10 everyday.txt: change "tracking branch" to "remote-tracking branch"Matthieu Moy, Nov 2, 2010
  6. 05/10 Change "tracking branch" to "remote-tracking branch"Matthieu Moy, Nov 2, 2010
  7. Santi BéjarNov 2, 2010
  8. Forgotten 'tracking' -> 'remote-tracking'Matthieu Moy, Nov 2, 2010
  9. 06/10 Change incorrect uses of "remote branch" meaning "remote-tracking"Matthieu Moy, Nov 2, 2010
  10. 07/10 Change incorrect "remote branch" to "remote tracking branch" in C codeMatthieu Moy, Nov 2, 2010
  11. What's the -s switch in git show?Will Hall, Nov 9, 2010
  12. Documentation: document show -sJonathan Nieder, Nov 9, 2010
  13. 08/10 user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Nov 2, 2010
  14. Peter KreftingNov 2, 2010
  15. user-manual.txt: explain better the remote(-tracking) branch termsMatthieu Moy, Nov 2, 2010
  16. 09/10 user-manual: remote-tracking can be checked out, with detached HEADMatthieu Moy, Nov 2, 2010
  17. 10/10 git-branch.txt: mention --set-upstream as a way to change upstream configurationMatthieu Moy, Nov 2, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.