# Wrong help text on git status -h ?

3 messages from 2008-04-23 to 2008-05-13. Participants: Stefan Näwe, Matthieu Moy.
Thread: https://gitlist.dev/t/13226

## Stefan Näwe, 2008-04-23 12:54

Subject: Wrong help text on git status -h ?
Message-ID: <loom.20080423T125136-135@post.gmane.org>
URL: https://gitlist.dev/e/loom.20080423T125136-135%40post.gmane.org

```
Hi all.

This is what I get:

~/src/git$ ./git version
git version 1.5.5.1.67.gbdb8


~/src/git$ ./git status -h
usage: git-status [options] [--] <filepattern>...

    -q, --quiet           be quiet
    -v, --verbose         be verbose

Commit message options
   [....]

Commit contents options
   [....]


(The [....] is deleted by me for this post!).

Getting help for commit on 'git status -h' can't be right, can it ?
Or am I missing something?

Thanks,
Stefan

```

## Matthieu Moy, 2008-04-23 16:00

Subject: Re: Wrong help text on git status -h ?
Message-ID: <vpqfxtc36j4.fsf@bauges.imag.fr>
URL: https://gitlist.dev/e/vpqfxtc36j4.fsf%40bauges.imag.fr
In-Reply-To: <loom.20080423T125136-135@post.gmane.org>

```
Stefan Näwe <stefan.naewe+git@gmail.com> writes:

> Getting help for commit on 'git status -h' can't be right, can it ?
> Or am I missing something?

I'd say: both.

git status could have been spelled "git commit --dry-run", they're
actually the same command, but "git status" stops before launching the
editor and doing the actual commit. So, they take the exact same set
of options.

That said, in an ideal world, "git status -h" would mention that the
commit message options are ignored with "git status".

-- 
Matthieu

```

## Stefan Näwe, 2008-05-13 11:09

Subject: Re: Wrong help text on git status -h ?
Message-ID: <loom.20080513T110711-862@post.gmane.org>
URL: https://gitlist.dev/e/loom.20080513T110711-862%40post.gmane.org
In-Reply-To: <vpqfxtc36j4.fsf@bauges.imag.fr>

```
Matthieu Moy <Matthieu.Moy <at> imag.fr> writes:

> 
> Stefan Näwe <stefan.naewe+git <at> gmail.com> writes:
> 
> > Getting help for commit on 'git status -h' can't be right, can it ?
> > Or am I missing something?
> 
> I'd say: both.

Well, I can't be *that* wrong:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478814

 
> git status could have been spelled "git commit --dry-run", they're
> actually the same command, but "git status" stops before launching the
> editor and doing the actual commit. So, they take the exact same set
> of options.
> 
> That said, in an ideal world, "git status -h" would mention that the
> commit message options are ignored with "git status".
> 

Regards,
   Stefan

```