From: David Greaves <david@dgreaves.com>
To: Junio C Hamano <junio@siamese.dyndns.org>
Cc: Petr Baudis <pasky@ucw.cz>, GIT Mailing Lists <git@vger.kernel.org>
Subject: Re: [PATCH] Docs update
Date: Fri, 22 Apr 2005 00:10:23 +0100 [thread overview]
Message-ID: <426832DF.4090909@dgreaves.com> (raw)
In-Reply-To: <7vy8bbd9n4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
>>>>>>"DG" == David Greaves <david@dgreaves.com> writes:
> Looks nice. I agree with Petr's comment that separating core part
> and Cogito part would be good
OK
> And the option to use working tree is not having the --cached
> flag you describe later. Please also update the usage at the
> top as well:
<snip>
> This command can take commit ID in place of tree ID.
Yep, the intention is to do all the core docs, get consistent use of
<sha1> or <tree> or <id> etc etc and then patch all the usage()s at once.
Thanks for the comments - will edit in the am.
David
prev parent reply other threads:[~2005-04-21 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 20:40 [PATCH] Docs update David Greaves
2005-04-21 20:43 ` Petr Baudis
2005-04-21 21:16 ` David Greaves
2005-04-21 21:26 ` Petr Baudis
2005-04-21 22:53 ` Junio C Hamano
2005-04-21 23:10 ` David Greaves [this message]
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=426832DF.4090909@dgreaves.com \
--to=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=junio@siamese.dyndns.org \
--cc=pasky@ucw.cz \
/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).