From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] make 'git add' a first class user friendly interface to the index
Date: Sat, 02 Dec 2006 10:52:33 +0100 [thread overview]
Message-ID: <ekri99$7gh$1@sea.gmane.org> (raw)
In-Reply-To: 7vpsb36yem.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> - We keep the word "index", and not reword it to "stage" in the
> names of commands and options. "to stage" is very good verb
> to explain the _concept_, but there is no need to use
> inconsistent wording Porcelain-ish and plumbing use to
> describe the entity used for staging.
>
> (1) New people need to learn the new concept anyway, and they
> are intelligent enough to learn what that new concept has
> been called for a long time in git-land at the same time.
>
> "The index" is the receiver of new contents to be staged;
> conversely, "to stage" is the act of registering contents
> to the index.
I think we should refer to "the index" as "the staging area [for commits]",
at least the first time (it is a bit longish to use it later).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-02 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:06 [PATCH] make 'git add' a first class user friendly interface to the index Nicolas Pitre
2006-12-01 22:31 ` Junio C Hamano
2006-12-02 0:18 ` Alan Chandler
2006-12-02 2:01 ` Nicolas Pitre
2006-12-02 3:05 ` Nicolas Pitre
2006-12-02 6:54 ` Carl Worth
2006-12-02 7:54 ` Junio C Hamano
2006-12-02 9:06 ` Carl Worth
2006-12-02 10:11 ` Jakub Narebski
2006-12-02 14:51 ` Han-Wen Nienhuys
2006-12-02 8:28 ` Alan Chandler
2006-12-02 16:49 ` Carl Worth
2006-12-02 17:12 ` Jakub Narebski
2006-12-02 18:05 ` Alan Chandler
2006-12-03 4:04 ` Nicolas Pitre
2006-12-03 4:22 ` Nicolas Pitre
2006-12-03 4:34 ` Nicolas Pitre
2006-12-02 9:52 ` Jakub Narebski [this message]
2006-12-03 5:03 ` Nicolas Pitre
2006-12-03 5:33 ` [PATCH v2] " Nicolas Pitre
2006-12-03 9:16 ` Alan Chandler
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='ekri99$7gh$1@sea.gmane.org' \
--to=jnareb@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).