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

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

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Oct 14, 2013, 14:36 UTC
Message-ID
<20131014143632.GD21200@google.com>
In-Reply-To
<1381760611-9573-1-git-send-email-boklm@mars-attacks.org>
Nicolas Vigier wrote:
> "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>
Thanks.
[...]
> --- a/Documentation/git-rev-parse.txt
> +++ b/Documentation/git-rev-parse.txt
> @@ -259,9 +259,10 @@ Each line of options has this format:
[...]
> -	* 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).
This still seems confusing: the argument's use is discouraged?
Would something like the following make sense?
	* Use `?` if [...]. This is used for historical options
	  that once took no argument and later gained an optional
	  argument. Use of this feature for new options is
	  discouraged.

Hope that helps, Jonathan

Previous: Nicolas VigierNext: Nicolas Vigier
Message 2 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.