git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Notes and questions while reading the documentation

From
CMChristian Meder <chris@absolutegiganten.org>
Date
Oct 5, 2005, 22:06 UTC
Message-ID
<1128549966.11363.29.camel@localhost>
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: Junio C Hamano
Message 1 of 3 in “Notes and questions while reading the documentation”
  1. Christian MederOct 5, 2005
  2. Junio C HamanoOct 5, 2005
  3. Christian MederOct 10, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.