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

Re: [PATCH] git.c: make usage match manual page

From
Kevin Bracey <kevin@bracey.fi>
Date
Mar 11, 2013, 20:43 UTC
Message-ID
<513E41E2.3060700@bracey.fi>
In-Reply-To
<7vli9t909a.fsf@alter.siamese.dyndns.org>
On 11/03/2013 21:58, Junio C Hamano wrote:
Show 5 quoted lines
> Kevin Bracey <kevin@bracey.fi> writes:
>
>> Re-ordered option list in command-line usage to match the manual page.
>> Also makes it less than 80-characters wide.
> Thanks (s/Re-ordered/reorder/ and s/makes/make/, though).

Got it. But I'm going to reword it, to follow the history of the manual change.

> Is git.c the only one whose "-h" output does not match the manual
> synopsis?
>

Generally, "-h" just puts "<options>" in the synopsis, and then prints a line per option, so most commands don't really match the manual "show all options on one line" style anyway. git.c is atypical. (Something else to look at for the whole git help thing? Should "git -h" print a option list in that style?)

But, yes, I've found a few others that are show almost the same thing as the manual but with subtle pointless differences. "git remote", for example. That's a larger project, I feel; the 80-column thing is key here.

Kevin
Previous: Junio C HamanoNext: Kevin Bracey
Message 3 of 4 in “git.c: make usage match manual page”
  1. git.c: make usage match manual pageKevin Bracey, Mar 11, 2013
  2. Junio C HamanoMar 11, 2013
  3. Kevin BraceyMar 11, 2013
  4. git.c: rearrange git synopsis to fit in 80 columnsKevin Bracey, Mar 11, 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.