From: A Large Angry SCM <gitzilla@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Missing documentation
Date: Mon, 05 Sep 2005 17:41:13 +0000 [thread overview]
Message-ID: <431C8339.7070505@gmail.com> (raw)
The following is the list of files in the Documentation directory that
have *NO* useful text in them at all.
git-build-rev-cache.txt
git-checkout-script.txt
git-diff-script.txt
git-format-patch-script.txt
git-get-tar-commit-id.txt
git-reset-script.txt
git-rev-parse.txt
git-show-rev-cache.txt
gitk.txt
The list is the output of the following trivial script:
cd Documentation
grep -l 'Does something not yet documented.' *
If you are the/an author of one or more of these commands (or anyone
else), please create some documentation for it.
If you care to, please review the rest of the documentation for out of
date and/or incomplete text and either produce a patch or let Junio know
so it can be added to the TODO list.
reply other threads:[~2005-09-05 17:41 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=431C8339.7070505@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 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).