From: A Large Angry SCM <gitzilla@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Documentation call for help
Date: Fri, 09 Sep 2005 11:11:34 -0400 [thread overview]
Message-ID: <4321A626.9040400@gmail.com> (raw)
The good news:
There is now some usable documentation for all the git commands except
for the following:
git-archimport (Martin?)
gitk (Paul?)
The bad news:
Some, if not most, of the command documentation is incomplete or
possibly incorrect. Mostly it's a case of the documentation not keeping
pace with changes in the code.
You can help by comparing the implementation of a command with it's
documentation and producing a patch to fix or, at least, improve the
documentation.
reply other threads:[~2005-09-09 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4321A626.9040400@gmail.com \
--to=gitzilla@gmail.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 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.