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

[PATCH] rev-parse doc: clarify use of optional / required arguments

From
Nicolas Vigier <boklm@mars-attacks.org>
Date
Oct 14, 2013, 14:23 UTC
Message-ID
<1381760611-9573-1-git-send-email-boklm@mars-attacks.org>

"the option is optional" was confusing as it is not the option but its argument which is optional.

Signed-off-by: Nicolas Vigier <boklm@mars-attacks.org>
---
 Documentation/git-rev-parse.txt | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-rev-parse.txt b/Documentation/git-rev-parse.txt
index 2b126c0..7ec9221 100644
--- a/Documentation/git-rev-parse.txt
+++ b/Documentation/git-rev-parse.txt
@@ -259,9 +259,10 @@ Each line of options has this format:
 
 `<flags>`::
 	`<flags>` are of `*`, `=`, `?` or `!`.
-	* Use `=` if the option takes an argument.
+	* Use `=` if the option requires an argument.
 
-	* Use `?` to mean that the option is optional (though its use is discouraged).
+	* Use `?` if the option takes an optional argument (though its use is
+	  discouraged).
 
 	* Use `*` to mean that this option should not be listed in the usage
 	  generated for the `-h` argument. It's shown for `--help-all` as
-- 
1.8.4
Next: Jonathan Nieder
Message 1 of 5 in “rev-parse doc: clarify use of optional / required arguments”
  1. rev-parse doc: clarify use of optional / required argumentsNicolas Vigier, Oct 14, 2013
  2. Jonathan NiederOct 14, 2013
  3. Nicolas VigierOct 14, 2013
  4. brian m. carlsonOct 14, 2013
  5. Nicolas VigierOct 15, 2013

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.