# Command-line options that lack documentation

4 messages from 2011-07-21 to 2011-07-21. Participants: Nikolai Weibull, Thomas Rast, Jens Lehmann.
Thread: https://gitlist.dev/t/27878

## Nikolai Weibull, 2011-07-21 12:07

Subject: Command-line options that lack documentation
Message-ID: <CADdV=MsNyhOg7r9NV67e0V1_7FCvdBu4YA=7gAEjPLagP0r9yw@mail.gmail.com>
URL: https://gitlist.dev/e/CADdV%3DMsNyhOg7r9NV67e0V1_7FCvdBu4YA%3D7gAEjPLagP0r9yw%40mail.gmail.com

```
Hi!

The following options lack (full) documentation in the manual pages:

git-am:
  --patch-format
  --rerere-autoupdate

git-bisect:
  next subcommand

git-commit:
  --null
  --interactive

git-notes copy:
  --for-rewrite

git-submodule update:
  --init

git-config:
  --local

git-reflog expire:
  -n, --dry-run

git-reflog delete:
  -n, --dry-run

git-repack:
  --quiet

git-cherry:
  --abbrev

git-fsck:
  -v

git-rerere:
  --rerere-autoupdate

git-verify-tag:
  -v, --verbose

git-svn init | fetch | clone | rebase | dcommit:
  --no-auth-cache
  --config-dir

git-svn fetch | clone | rebase | dcommit:
  --noMetadata
  --useSvmProps
  --useSvnsyncProps
  --log-window-size
  --no-checkout

git-svn fetch | rebase | dcommit:
  --fetch-all, --all

git-svn dcommit:
  -C, --copy-similarity

git-svn log:
  --color
  --pager
  --non-recursive

git-svn show-ignore | mkdirs:
  -r, --revision

git-svn commit-diff:
  -m, --message
  -F, --file
  -r, --revision

git-index-pack:
  --pack_header

git-merge-file:
  --marker-size
  --diff3

git-pack-objects:
  --reflog
  --keep-unreachable
  --unpack-unreachable

git-ls-files:
  --resolve-undo

git-send-pack:
  --mirror
  --stateless-rpc
  --helper-status

git-receive-pack:
  --advertise-refs
  --stateless-rpc

git-upload-pack:
  --advertise-refs
  --stateless-rpc

git-mailinfo:
  --no-inbody-headers

Furthermore, the fact that most commands take -h and --help is
undocumented, but perhaps not of any real importance.

I would provide patches to the documentation, but most of these
options are beyond my grasp of Git.

```

## Thomas Rast, 2011-07-21 12:34

Subject: Re: Command-line options that lack documentation
Message-ID: <201107211434.29677.trast@student.ethz.ch>
URL: https://gitlist.dev/e/201107211434.29677.trast%40student.ethz.ch
In-Reply-To: <CADdV=MsNyhOg7r9NV67e0V1_7FCvdBu4YA=7gAEjPLagP0r9yw@mail.gmail.com>

```
Nikolai Weibull wrote:
> 
> The following options lack (full) documentation in the manual pages:
[...]
> git-notes copy:
>   --for-rewrite

Intentional, cf. 6956f85 (notes: implement helpers needed for note
copying during rewrite, 2010-03-12).

> Furthermore, the fact that most commands take -h and --help is
> undocumented, but perhaps not of any real importance.

It's actually in gitcli(7).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

```

## Jens Lehmann, 2011-07-21 20:18

Subject: Re: Command-line options that lack documentation
Message-ID: <4E288993.3030005@web.de>
URL: https://gitlist.dev/e/4E288993.3030005%40web.de
In-Reply-To: <CADdV=MsNyhOg7r9NV67e0V1_7FCvdBu4YA=7gAEjPLagP0r9yw@mail.gmail.com>

```
Am 21.07.2011 14:07, schrieb Nikolai Weibull:
> Hi!
> 
> The following options lack (full) documentation in the manual pages:

<snip>

> git-submodule update:
>   --init

"--init" is documented in the synopsis and under the "init" and "update"
commands. The only shortcoming is that the "--init" option isn't quoted
properly and thus doesn't get decorated like other options in the html
pages, is that what you mean?

```

## Nikolai Weibull, 2011-07-21 21:09

Subject: Re: Command-line options that lack documentation
Message-ID: <CADdV=Ms6vK0vLV4sy-bGmD7raTKtEMCK_R4UqhyKNz8Q4T05Ug@mail.gmail.com>
URL: https://gitlist.dev/e/CADdV%3DMs6vK0vLV4sy-bGmD7raTKtEMCK_R4UqhyKNz8Q4T05Ug%40mail.gmail.com
In-Reply-To: <4E288993.3030005@web.de>

```
On Thu, Jul 21, 2011 at 22:18, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> Am 21.07.2011 14:07, schrieb Nikolai Weibull:

>> The following options lack (full) documentation in the manual pages:

>> git-submodule update:
>>   --init

> "--init" is documented in the synopsis and under the "init" and "update"
> commands.

While that’s true, It’s not documented under the OPTIONS header.

```