From: Jens Lehmann <Jens.Lehmann@web.de>
To: Nikolai Weibull <now@bitwi.se>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Command-line options that lack documentation
Date: Thu, 21 Jul 2011 22:18:27 +0200 [thread overview]
Message-ID: <4E288993.3030005@web.de> (raw)
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?
next prev parent reply other threads:[~2011-07-21 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 12:07 Command-line options that lack documentation Nikolai Weibull
2011-07-21 12:34 ` Thomas Rast
2011-07-21 20:18 ` Jens Lehmann [this message]
2011-07-21 21:09 ` Nikolai Weibull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E288993.3030005@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=now@bitwi.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).