From: Nicolas Pitre <nico@cam.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-commit: rewrite to make it more end-user friendly.
Date: Sun, 10 Dec 2006 17:07:40 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612101704390.2630@xanadu.home> (raw)
In-Reply-To: <20061210210057.GB23387@fieldses.org>
On Sun, 10 Dec 2006, J. Bruce Fields wrote:
> Or maybe: "by using gitlink:git-add[1] to add new content (of either new
> or newly modified files) to the next commit."
>
> Man pages are reference documentation, so I figure it's OK to sacrifice
> a little newbie-friendliness for accuracy and concision.
I disagree. Clarity should be the first goal. And the fact that even
modified files have to be specified is something worth enphasizing,
especially since this is not something other systems do.
next prev parent reply other threads:[~2006-12-10 22:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 11:20 Documentation/git-commit.txt Junio C Hamano
2006-12-08 11:55 ` Documentation/git-commit.txt Salikh Zakirov
2006-12-08 19:31 ` Documentation/git-commit.txt Junio C Hamano
2006-12-08 19:45 ` Documentation/git-commit.txt Nicolas Pitre
2006-12-08 22:56 ` Documentation/git-commit.txt Alan Chandler
2006-12-10 0:11 ` Documentation/git-commit.txt Horst H. von Brand
2006-12-10 9:23 ` Documentation/git-commit.txt Alan Chandler
2006-12-11 14:58 ` Documentation/git-commit.txt Andreas Ericsson
2006-12-09 2:58 ` Documentation/git-commit.txt Nicolas Pitre
2006-12-09 4:25 ` Documentation/git-commit.txt Junio C Hamano
2006-12-09 4:42 ` Documentation/git-commit.txt J. Bruce Fields
2006-12-09 19:58 ` Documentation/git-commit.txt Nicolas Pitre
2006-12-09 20:49 ` Documentation/git-commit.txt Jakub Narebski
2006-12-09 5:48 ` [PATCH] Documentation/git-commit: rewrite to make it more end-user friendly Junio C Hamano
2006-12-09 21:15 ` Nicolas Pitre
2006-12-09 21:59 ` Junio C Hamano
2006-12-09 22:05 ` Jakub Narebski
2006-12-09 22:19 ` Linus Torvalds
2006-12-09 22:24 ` Jakub Narebski
2006-12-09 22:26 ` Nicolas Pitre
2006-12-10 0:30 ` Josef Weidendorfer
2006-12-10 0:51 ` Nicolas Pitre
2006-12-10 21:00 ` J. Bruce Fields
2006-12-10 22:07 ` Nicolas Pitre [this message]
2006-12-10 22:41 ` J. Bruce Fields
2006-12-10 23:05 ` Junio C Hamano
2006-12-10 9:17 ` Alan Chandler
2006-12-09 4:31 ` Documentation/git-commit.txt J. Bruce Fields
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=Pine.LNX.4.64.0612101704390.2630@xanadu.home \
--to=nico@cam.org \
--cc=Josef.Weidendorfer@gmx.de \
--cc=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).