{"thread":{"id":"33157","subject":"[PATCH] git.c: make usage match manual page","startedAt":"2013-03-11T19:44:15Z","lastAt":"2013-03-11T20:44:10Z","messageCount":4,"participants":["Kevin Bracey","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"211072","messageId":"1363031055-13562-1-git-send-email-kevin@bracey.fi","threadId":"33157","inReplyTo":null,"subject":"[PATCH] git.c: make usage match manual page","fromName":"Kevin Bracey","fromEmail":"kevin@bracey.fi","sentAt":"2013-03-11T19:44:15Z","receivedAt":"2013-03-11T19:44:15Z","isPatch":true,"sender":{"key":"kevin@bracey.fi","avatar":"https://avatars.githubusercontent.com/u/96079793?v=4"},"body":"Re-ordered option list in command-line usage to match the manual page.\nAlso makes it less than 80-characters wide.\n\nSigned-off-by: Kevin Bracey \n---\n git.c | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/git.c b/git.c\nindex d33f9b3..2a98624 100644\n--- a/git.c\n+++ b/git.c\n@@ -6,10 +6,10 @@\n #include \"run-command.h\"\n \n const char git_usage_string[] =\n-\t\"git [--version] [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n+\t\"git [--version] [--help] [-c name=value]\\n\"\n+\t\" [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n \t\" [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]\\n\"\n \t\" [--git-dir=] [--work-tree=] [--namespace=]\\n\"\n-\t\" [-c name=value] [--help]\\n\"\n \t\" []\";\n \n const char git_more_info_string[] =\n-- \n1.8.2.rc3.7.g1100d09.dirty\n"},{"id":"211073","messageId":"7vli9t909a.fsf@alter.siamese.dyndns.org","threadId":"33157","inReplyTo":"1363031055-13562-1-git-send-email-kevin@bracey.fi","subject":"Re: [PATCH] git.c: make usage match manual page","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-03-11T19:58:41Z","receivedAt":"2013-03-11T19:58:41Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Kevin Bracey writes:\n\n> Re-ordered option list in command-line usage to match the manual page.\n> Also makes it less than 80-characters wide.\n\nThanks (s/Re-ordered/reorder/ and s/makes/make/, though).\n\nIs git.c the only one whose \"-h\" output does not match the manual\nsynopsis?\n\n>\n> Signed-off-by: Kevin Bracey \n> ---\n> git.c | 4 ++--\n> 1 file changed, 2 insertions(+), 2 deletions(-)\n>\n> diff --git a/git.c b/git.c\n> index d33f9b3..2a98624 100644\n> --- a/git.c\n> +++ b/git.c\n> @@ -6,10 +6,10 @@\n> #include \"run-command.h\"\n> \n> const char git_usage_string[] =\n> -\t\"git [--version] [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n> +\t\"git [--version] [--help] [-c name=value]\\n\"\n> +\t\" [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n> \t\" [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]\\n\"\n> \t\" [--git-dir=] [--work-tree=] [--namespace=]\\n\"\n> -\t\" [-c name=value] [--help]\\n\"\n> \t\" []\";\n> \n> const char git_more_info_string[] =\n"},{"id":"211075","messageId":"513E41E2.3060700@bracey.fi","threadId":"33157","inReplyTo":"7vli9t909a.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] git.c: make usage match manual page","fromName":"Kevin Bracey","fromEmail":"kevin@bracey.fi","sentAt":"2013-03-11T20:43:14Z","receivedAt":"2013-03-11T20:43:14Z","isPatch":true,"sender":{"key":"kevin@bracey.fi","avatar":"https://avatars.githubusercontent.com/u/96079793?v=4"},"body":"On 11/03/2013 21:58, Junio C Hamano wrote:\n> Kevin Bracey writes:\n>\n>> Re-ordered option list in command-line usage to match the manual page.\n>> Also makes it less than 80-characters wide.\n> Thanks (s/Re-ordered/reorder/ and s/makes/make/, though).\n\nGot it. But I'm going to reword it, to follow the history of the manual \nchange.\n\n> Is git.c the only one whose \"-h\" output does not match the manual\n> synopsis?\n>\nGenerally, \"-h\" just puts \"\" in the synopsis, and then prints a \nline per option, so most commands don't really match the manual \"show \nall options on one line\" style anyway. git.c is atypical. (Something \nelse to look at for the whole git help thing? Should \"git -h\" print a \noption list in that style?)\n\nBut, yes, I've found a few others that are show almost the same thing as \nthe manual but with subtle pointless differences. \"git remote\", for \nexample. That's a larger project, I feel; the 80-column thing is key here.\n\nKevin\n"},{"id":"211076","messageId":"1363034650-14984-1-git-send-email-kevin@bracey.fi","threadId":"33157","inReplyTo":"1363031055-13562-1-git-send-email-kevin@bracey.fi","subject":"[PATCH] git.c: rearrange git synopsis to fit in 80 columns","fromName":"Kevin Bracey","fromEmail":"kevin@bracey.fi","sentAt":"2013-03-11T20:44:10Z","receivedAt":"2013-03-11T20:44:10Z","isPatch":true,"sender":{"key":"kevin@bracey.fi","avatar":"https://avatars.githubusercontent.com/u/96079793?v=4"},"body":"Make the command line use the narrower synopsis layout that the man page\nhas used since commit 68e4b55.\n\nSigned-off-by: Kevin Bracey \n---\n git.c | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/git.c b/git.c\nindex d33f9b3..2a98624 100644\n--- a/git.c\n+++ b/git.c\n@@ -6,10 +6,10 @@\n #include \"run-command.h\"\n \n const char git_usage_string[] =\n-\t\"git [--version] [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n+\t\"git [--version] [--help] [-c name=value]\\n\"\n+\t\" [--exec-path[=]] [--html-path] [--man-path] [--info-path]\\n\"\n \t\" [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]\\n\"\n \t\" [--git-dir=] [--work-tree=] [--namespace=]\\n\"\n-\t\" [-c name=value] [--help]\\n\"\n \t\" []\";\n \n const char git_more_info_string[] =\n-- \n1.8.2.rc3.7.g1100d09.dirty\n"}]}