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

Re: [PATCH] git-rebase.sh: Update USAGE string (No. 1)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 4, 2008, 00:24 UTC
Message-ID
<7vodaxpo0i.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<m3lk6161jo.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> writes:
> Besides here the mutually exclusive options are naturelly delimited,
> so you can say just (I think):
>    [--whitespace=nowarn|warn|error|error-all|strip]

I think that is probably the right thing to do in this case. It is clear where the alternatives end, without adding extra grouping, so it keeps the description easy to read.

It may fail with a sick reader who would complain "but 'git rebase --whitespace=nowarn' is correct while 'git rebase warn' is not!", but personally I do not think we deeply care about pleasing such a pedantic nitpicker.

Previous: Jakub NarebskiNext: Jari Aalto
Message 12 of 20 in “git-rebase.sh: Update USAGE string”
  1. git-rebase.sh: Update USAGE stringJari Aalto, Feb 3, 2008
  2. Jakub NarebskiFeb 3, 2008
  3. git-rebase.sh: Update USAGE string (No. 1)Jari Aalto, Feb 3, 2008
  4. Johannes SchindelinFeb 3, 2008
  5. Jakub NarebskiFeb 3, 2008
  6. Jari AaltoFeb 4, 2008
  7. Johannes SchindelinFeb 4, 2008
  8. Junio C HamanoFeb 4, 2008
  9. Jakub NarebskiFeb 4, 2008
  10. Mike HommeyFeb 4, 2008
  11. Jakub NarebskiFeb 4, 2008
  12. Junio C HamanoFeb 4, 2008
  13. git-rebase.sh: Update USAGE stringJari Aalto, Feb 4, 2008
  14. しらいしななこFeb 4, 2008
  15. rebase -i and --whitespace, was Re: [PATCH] git-rebase.sh: Update USAGE string (No. 1)Johannes Schindelin, Feb 4, 2008
  16. Jakub NarebskiFeb 4, 2008
  17. Johannes SchindelinFeb 4, 2008
  18. Junio C HamanoFeb 5, 2008
  19. Johannes SchindelinFeb 6, 2008
  20. git-rebase.sh: Update USAGE stringJari Aalto, Feb 4, 2008

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.