{"thread":{"id":"13226","subject":"Wrong help text on git status -h ?","startedAt":"2008-04-23T12:54:51Z","lastAt":"2008-05-13T11:09:06Z","messageCount":3,"participants":["Stefan Näwe","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"75058","messageId":"loom.20080423T125136-135@post.gmane.org","threadId":"13226","inReplyTo":null,"subject":"Wrong help text on git status -h ?","fromName":"Stefan Näwe","fromEmail":"stefan.naewe+git@gmail.com","sentAt":"2008-04-23T12:54:51Z","receivedAt":"2008-04-23T12:54:51Z","isPatch":false,"sender":{"key":"stefan.naewe+git@gmail.com","avatar":"https://gravatar.com/avatar/ff9c89e7b42e5c7f494ef0f19ac9bde6693fb6465356711b8d4ed47d2108dd46?d=mp&s=160"},"body":"Hi all.\n\nThis is what I get:\n\n~/src/git$ ./git version\ngit version 1.5.5.1.67.gbdb8\n\n\n~/src/git$ ./git status -h\nusage: git-status [options] [--] <filepattern>...\n\n    -q, --quiet           be quiet\n    -v, --verbose         be verbose\n\nCommit message options\n   [....]\n\nCommit contents options\n   [....]\n\n\n(The [....] is deleted by me for this post!).\n\nGetting help for commit on 'git status -h' can't be right, can it ?\nOr am I missing something?\n\nThanks,\nStefan\n"},{"id":"75072","messageId":"vpqfxtc36j4.fsf@bauges.imag.fr","threadId":"13226","inReplyTo":"loom.20080423T125136-135@post.gmane.org","subject":"Re: Wrong help text on git status -h ?","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@imag.fr","sentAt":"2008-04-23T16:00:47Z","receivedAt":"2008-04-23T16:00:47Z","isPatch":false,"sender":{"key":"git@matthieu-moy.fr","avatar":"https://avatars.githubusercontent.com/u/14709?v=4"},"body":"Stefan Näwe <stefan.naewe+git@gmail.com> writes:\n\n> Getting help for commit on 'git status -h' can't be right, can it ?\n> Or am I missing something?\n\nI'd say: both.\n\ngit status could have been spelled \"git commit --dry-run\", they're\nactually the same command, but \"git status\" stops before launching the\neditor and doing the actual commit. So, they take the exact same set\nof options.\n\nThat said, in an ideal world, \"git status -h\" would mention that the\ncommit message options are ignored with \"git status\".\n\n-- \nMatthieu\n"},{"id":"76859","messageId":"loom.20080513T110711-862@post.gmane.org","threadId":"13226","inReplyTo":"vpqfxtc36j4.fsf@bauges.imag.fr","subject":"Re: Wrong help text on git status -h ?","fromName":"Stefan Näwe","fromEmail":"stefan.naewe+git@gmail.com","sentAt":"2008-05-13T11:09:06Z","receivedAt":"2008-05-13T11:09:06Z","isPatch":false,"sender":{"key":"stefan.naewe+git@gmail.com","avatar":"https://gravatar.com/avatar/ff9c89e7b42e5c7f494ef0f19ac9bde6693fb6465356711b8d4ed47d2108dd46?d=mp&s=160"},"body":"Matthieu Moy <Matthieu.Moy <at> imag.fr> writes:\n\n> \n> Stefan Näwe <stefan.naewe+git <at> gmail.com> writes:\n> \n> > Getting help for commit on 'git status -h' can't be right, can it ?\n> > Or am I missing something?\n> \n> I'd say: both.\n\nWell, I can't be *that* wrong:\n\nhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478814\n\n \n> git status could have been spelled \"git commit --dry-run\", they're\n> actually the same command, but \"git status\" stops before launching the\n> editor and doing the actual commit. So, they take the exact same set\n> of options.\n> \n> That said, in an ideal world, \"git status -h\" would mention that the\n> commit message options are ignored with \"git status\".\n> \n\nRegards,\n   Stefan\n"}]}