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

Re: [PATCHv2 00/10] Cleaning up --help-all inconsistencies

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Feb 16, 2011, 07:46 UTC
Message-ID
<4D5B80E9.90606@drmicha.warpmail.net>
In-Reply-To
<7v1v39p1cv.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 15.02.2011 20:02:
Show 14 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> 
>> v2 incorporates the changes as discussed so far.
> 
> Looked reasonable; thanks.
> 
>> It comes with three bonus patches which enforce the use of lowercase
>> <identifiers> (as per CodingGuidelines) in command messages (usage).
>>
>> Besides the guidelines, this is also the prevailing style in code.
> 
> Not that I am opposed to this change, but I don't see anything that says
> we want lower-case in CodingGuidelines. "Placeholders are enclosed in
> angle brackets." is the only thing it says as far as I can tell.

It's not expressed explicitly, but the examples there are all lowercase. Your patch below makes it explicit.

Having a second look at documentation, there aren't many changes to do - I would tend to leave things like <URL>, <FQDN>, possibly <UUID> (since they are abbreviations) uppercase; unsure about <CVSROOT> (like the env var). What do you think?

Show 26 quoted lines
> So perhaps insert this before the last three patches.
> 
> -- >8 --
> Subject: CodingGuidelines: downcase placeholders in usage messages
> 
> We accumulated some inconsistencies without an explicit guidance to spell
> this out over time.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  Documentation/CodingGuidelines |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines
> index ba2006d..fe1c1e5 100644
> --- a/Documentation/CodingGuidelines
> +++ b/Documentation/CodingGuidelines
> @@ -152,7 +152,7 @@ Writing Documentation:
>   when writing or modifying command usage strings and synopsis sections
>   in the manual pages:
>  
> - Placeholders are enclosed in angle brackets:
> + Placeholders are spelled in lowercase and enclosed in angle brackets:
>     <file>
>     --sort=<key>
>     --abbrev[=<n>]
Previous: Junio C HamanoNext: Junio C Hamano
Message 24 of 36 in “Cleaning up --help-all inconsistencies”
  1. 0/7 Cleaning up --help-all inconsistenciesMichael J Gruber, Feb 14, 2011
  2. 1/7 commit,tag: use same wording for -FMichael J Gruber, Feb 14, 2011
  3. Junio C HamanoFeb 14, 2011
  4. 2/7 push: describe --porcelain just like commit and statusMichael J Gruber, Feb 14, 2011
  5. Johannes SixtFeb 14, 2011
  6. Junio C HamanoFeb 14, 2011
  7. Sverre RabbelierFeb 14, 2011
  8. Michael J GruberFeb 15, 2011
  9. 3/7 clone,init: describe --template using the same wordingMichael J Gruber, Feb 14, 2011
  10. Junio C HamanoFeb 14, 2011
  11. 4/7 merge,tag: describe -m just like commitMichael J Gruber, Feb 14, 2011
  12. Junio C HamanoFeb 14, 2011
  13. Michael J GruberFeb 15, 2011
  14. Junio C HamanoFeb 15, 2011
  15. 5/7 add: describe --patch like checkout, resetMichael J Gruber, Feb 14, 2011
  16. 6/7 commit,status: describe -u likewiseMichael J Gruber, Feb 14, 2011
  17. Junio C HamanoFeb 14, 2011
  18. Michael J GruberFeb 15, 2011
  19. Jeff KingFeb 15, 2011
  20. 7/7 git-tag.txt: list all modes in the descriptionMichael J Gruber, Feb 14, 2011
  21. Junio C HamanoFeb 14, 2011
  22. 00/10 Cleaning up --help-all inconsistenciesMichael J Gruber, Feb 15, 2011
  23. Junio C HamanoFeb 15, 2011
  24. Michael J GruberFeb 16, 2011
  25. Junio C HamanoFeb 16, 2011
  26. Make <identifier> lowercase in DocumentationMichael J Gruber, Feb 17, 2011
  27. 01/10 commit,tag: use same wording for -FMichael J Gruber, Feb 15, 2011
  28. 02/10 commit,status: describe --porcelain just like pushMichael J Gruber, Feb 15, 2011
  29. 03/10 clone,init: describe --template using the same wordingMichael J Gruber, Feb 15, 2011
  30. 04/10 commit,merge,tag: describe -m likewiseMichael J Gruber, Feb 15, 2011
  31. 05/10 add: describe --patch like checkout, resetMichael J Gruber, Feb 15, 2011
  32. 06/10 commit,status: describe -u likewiseMichael J Gruber, Feb 15, 2011
  33. 07/10 git-tag.txt: list all modes in the descriptionMichael J Gruber, Feb 15, 2011
  34. 08/10 Make <identifier> lowercase as per CodingGuidelinesMichael J Gruber, Feb 15, 2011
  35. 09/10 Make <identifier> lowercase as per CodingGuidelinesMichael J Gruber, Feb 15, 2011
  36. 10/10 Make <identifier> lowercase as per CodingGuidelinesMichael J Gruber, Feb 15, 2011

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.