From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Documentation/git-commit.txt
Date: Fri, 8 Dec 2006 23:31:23 -0500 [thread overview]
Message-ID: <20061209043123.GB18204@fieldses.org> (raw)
In-Reply-To: <7vy7pik51b.fsf@assigned-by-dhcp.cox.net>
On Fri, Dec 08, 2006 at 03:20:32AM -0800, Junio C Hamano wrote:
> I think I went overboard and ended up not using the word
> "index", but eradicating the word was not my intention.
Yeah, "index" is a perfectly OK word, and it's already used all over the
documentation.
I think what you want to avoid is a huge digression into blobs, trees,
SHA1's, and the structure of the index file when you could just slip it
in there without a lot of fanfare, maybe like:
> +When recoring your own work, the contents of modified files in
> +your working tree are staged with gitlink:git-add[1].
^^^
...are temporarily stored to a staging area called the "index" with...
(though maybe that's a little cumbersome).
Also, I don't think there's anything wrong with the verb "stage", but I
think it may be a little less commonly used (in this meaning) than the
term "staging area", so people might catch on faster if we started with
"staging area".
prev parent reply other threads:[~2006-12-09 4:31 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
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 ` J. Bruce Fields [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=20061209043123.GB18204@fieldses.org \
--to=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).