From: "Chris Riddoch" <riddochc@gmail.com>
To: git@vger.kernel.org
Subject: A documentation to-do list
Date: Tue, 21 Nov 2006 18:13:12 -0700 [thread overview]
Message-ID: <6efbd9b70611211713y4a1574adje48622f7bab6d702@mail.gmail.com> (raw)
Hi, everyone.
Having decided to take it on myself to improve Git's documentation, I
asked on #git if people had particular things they felt I should focus
on. I also was prompted to put up a page on the wiki to make my to-do
list public.
So, I present: http://git.or.cz/gitwiki/Documentation_To-Do_List
Add your favorite, specific, lack-of-documentation or badly-described
annoyance here!
--
epistemological humility
next reply other threads:[~2006-11-22 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 1:13 Chris Riddoch [this message]
2006-11-22 1:33 ` A documentation to-do list Junio C Hamano
2006-11-22 5:29 ` Alan Chandler
2006-11-22 9:57 ` Johannes Schindelin
2006-11-22 17:18 ` Michael K. Edwards
2006-11-22 20:31 ` lamikr
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=6efbd9b70611211713y4a1574adje48622f7bab6d702@mail.gmail.com \
--to=riddochc@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).