From: Christian Meder <chris@absolutegiganten.org>
To: git@vger.kernel.org
Subject: Notes and questions while reading the documentation
Date: Thu, 06 Oct 2005 00:06:06 +0200 [thread overview]
Message-ID: <1128549966.11363.29.camel@localhost> (raw)
Hi,
while (proof-)reading the Documentation I noted down some remarks and
questions:
* a lot of the manpages include something like "v0.1, June 2005" in the
header; these versions tags are pretty obscure to interpret, timestamp
when last edited ? version of the manpage ? version of git when the
manpage was included ? maturity the author assigned to the content ?
If these tags don't follow some sane schema they should be removed.
* git-applymbox: -q for interactivity seems like a strange choice, ok I
knew -i for interactive and -q for quiet but -q for interactive editing
is _not_ really intuitive
* the usage of git, Git and GIT isn't consistent in the documentation.
I'd vote for only using git.
* git-clone says that http transport is not supported yet I used it to
clone the git repo from kernel.org yesterday. Should the documentation
get updated ?
* the manpage synopsises aren't consistent wrt command naming; it's "git
commit" but "git-branch"; I guess all the manpages should reference
their commands as "git-x" and not "git x"
Greetings,
Christian
--
Christian Meder, email: chris@absolutegiganten.org
The Way-Seeking Mind of a tenzo is actualized
by rolling up your sleeves.
(Eihei Dogen Zenji)
next reply other threads:[~2005-10-05 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 22:06 Christian Meder [this message]
2005-10-05 23:30 ` Notes and questions while reading the documentation Junio C Hamano
2005-10-10 21:22 ` Christian Meder
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=1128549966.11363.29.camel@localhost \
--to=chris@absolutegiganten.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.