From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
git@vger.kernel.org, "Jonathan Nieder" <jrnieder@gmail.com>,
"Jeff King" <peff@peff.net>, "Scott Chacon" <schacon@gmail.com>,
"Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
"Jakub Narębski" <jnareb@gmail.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>,
"Piotr Krukowiecki" <piotr.krukowiecki.news@gmail.com>
Subject: Re: [1.8.0] use 'stage' term consistently
Date: Wed, 09 May 2012 19:25:13 +0200 [thread overview]
Message-ID: <vpqehqtferq.fsf@bauges.imag.fr> (raw)
In-Reply-To: <CAMP44s0DRrqMdHzOBTeQGmKtP7LzFerLZTaNgbHfj0XtebW9wA@mail.gmail.com> (Felipe Contreras's message of "Wed, 9 May 2012 15:10:28 +0200")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Tue, May 8, 2012 at 6:06 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> The word "index" is quite well understood: that which points at the
>> information given a headword that refers to it, which is exactly what the
>> "index" we have is. On the other hand, "to stage/staging area" is not as
>> widely used outside the narrow shipping/logistics circles.
>
> That's what git has, *internally*, but that's not how high-level users
> interact with it.
I agree with that. Explaining users that the <whatever you call it> is
the place where you stage content in preparation for the next commit is
much more productive than explaining that it is an array of
(name, sha1sum) pairs.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2012-05-09 17:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 13:04 [1.8.0] use 'stage' term consistently Felipe Contreras
2012-05-05 16:52 ` Philip Oakley
2012-05-05 17:30 ` Felipe Contreras
2012-05-05 19:53 ` Philip Oakley
2012-05-06 9:53 ` Zbigniew Jędrzejewski-Szmek
2012-05-06 10:21 ` Jakub Narebski
2012-05-06 10:39 ` Matthieu Moy
2012-05-06 20:15 ` Felipe Contreras
2012-05-06 21:21 ` Jakub Narebski
2012-05-08 3:51 ` Junio C Hamano
2012-05-06 21:09 ` Felipe Contreras
2012-05-06 10:26 ` Matthieu Moy
2012-05-06 21:16 ` Felipe Contreras
2012-05-06 21:30 ` Ævar Arnfjörð Bjarmason
2012-05-07 17:52 ` Junio C Hamano
2012-05-07 20:05 ` Ævar Arnfjörð Bjarmason
2012-05-08 4:06 ` Junio C Hamano
2012-05-08 8:55 ` Ævar Arnfjörð Bjarmason
2012-05-08 14:53 ` Junio C Hamano
2012-05-09 13:10 ` Felipe Contreras
2012-05-09 17:25 ` Matthieu Moy [this message]
2012-05-19 0:50 ` Mark Lodato
2012-05-19 6:00 ` Jonathan Nieder
2012-05-19 6:32 ` Jonathan Nieder
2012-05-20 12:04 ` Felipe Contreras
2012-05-20 18:06 ` Jonathan Nieder
2012-05-19 10:14 ` Philip Oakley
2012-05-20 11:49 ` Felipe Contreras
2012-05-20 17:58 ` Jonathan Nieder
2012-05-20 21:11 ` Junio C Hamano
2012-05-21 1:12 ` Felipe Contreras
2012-05-21 1:32 ` Jonathan Nieder
2012-05-18 20:34 ` Thiago Farina
2012-05-08 14:01 ` Sebastien Douche
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=vpqehqtferq.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=avarab@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=jrnieder@gmail.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=peff@peff.net \
--cc=piotr.krukowiecki.news@gmail.com \
--cc=schacon@gmail.com \
/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).