From: Jon Loeliger <jdl@freescale.com>
To: git@vger.kernel.org
Subject: Documentation Directions
Date: Sun, 06 Nov 2005 11:35:14 -0600 [thread overview]
Message-ID: <E1EYoQE-0002QX-VM@jdl.com> (raw)
Couple of questions regarding documentation direction:
- Is the plan to update all docs to use $GIT_DIR instead of .git?
- Do we intend on adding explicit support for '--help' on most,
if not all, of the git commands? In some cases (git-branch)
a -*) case tacitly catches --help and usage()'s it. In other
cases (git-pull) this can't be done as -*) passes options
on to git-fetch. I think that we should catch --help directly
so that it doesn't emit git-fetch's *) catch-all usage:
% git pull --help
usage: git-fetch-pack [-q] [-v] [--exec=upload-pack] [host:]directory <refs>...
Fetch failure: --help
- Do you want to head in the per-man-page-"Now What?" direction
as suggested by Junio?
Thanks,
jdl
next reply other threads:[~2005-11-06 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 17:35 Jon Loeliger [this message]
2005-11-06 20:11 ` Documentation Directions Junio C Hamano
2005-11-06 22:03 ` Nikolai Weibull
-- strict thread matches above, loose matches on Subject: below --
2005-11-06 19:28 Jon Loeliger
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=E1EYoQE-0002QX-VM@jdl.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.org \
/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).