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

[PATCH] doc/for-each-ref: explicitly specify option names

From
Kevin Daudt <me@ikke.info>
Date
Sep 1, 2017, 14:49 UTC
Message-ID
<20170901144931.26114-1-me@ikke.info>

For count, sort and format, only the argument names were listed under OPTIONS, not the option names.

Add the option names to make it clear the options exist
Signed-off-by: Kevin Daudt <me@ikke.info>
---
 Documentation/git-for-each-ref.txt | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/git-for-each-ref.txt b/Documentation/git-for-each-ref.txt
index bb370c9c7..0c2032855 100644
--- a/Documentation/git-for-each-ref.txt
+++ b/Documentation/git-for-each-ref.txt
@@ -25,19 +25,25 @@ host language allowing their direct evaluation in that language.
 
 OPTIONS
 -------
-<count>::
+<pattern>...::
+	If one or more patterns are given, only refs are shown that
+	match against at least one pattern, either using fnmatch(3) or
+	literally, in the latter case matching completely or from the
+	beginning up to a slash.
+
+--count <count>::
 	By default the command shows all refs that match
 	`<pattern>`.  This option makes it stop after showing
 	that many refs.
 
-<key>::
+--sort <key>::
 	A field name to sort on.  Prefix `-` to sort in
 	descending order of the value.  When unspecified,
 	`refname` is used.  You may use the --sort=<key> option
 	multiple times, in which case the last key becomes the primary
 	key.
 
-<format>::
+--format <format>::
 	A string that interpolates `%(fieldname)` from a ref being shown
 	and the object it points at.  If `fieldname`
 	is prefixed with an asterisk (`*`) and the ref points
@@ -50,12 +56,6 @@ OPTIONS
 	`xx`; for example `%00` interpolates to `\0` (NUL),
 	`%09` to `\t` (TAB) and `%0a` to `\n` (LF).
 
-<pattern>...::
-	If one or more patterns are given, only refs are shown that
-	match against at least one pattern, either using fnmatch(3) or
-	literally, in the latter case matching completely or from the
-	beginning up to a slash.
-
 --shell::
 --perl::
 --python::
-- 
2.14.1.459.g238e487ea9
Next: Jeff King
Message 1 of 9 in “doc/for-each-ref: explicitly specify option names”
  1. doc/for-each-ref: explicitly specify option namesKevin Daudt, Sep 1, 2017
  2. Jeff KingSep 1, 2017
  3. Johannes SchindelinSep 1, 2017
  4. Jonathan NiederSep 1, 2017
  5. Junio C HamanoSep 2, 2017
  6. 1/2 doc/for-each-ref: consistently use '=' to between argument names and valuesKevin Daudt, Sep 11, 2017
  7. 2/2 doc/for-each-ref: explicitly specify option namesKevin Daudt, Sep 11, 2017
  8. Junio C HamanoSep 12, 2017
  9. Kevin DaudtSep 12, 2017

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.