From: Mark Lodato <lodatom@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð" <avarab@gmail.com>,
"Felipe Contreras" <felipe.contreras@gmail.com>,
"Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
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: Fri, 18 May 2012 20:50:55 -0400 [thread overview]
Message-ID: <CAHREChgTHZL0sNJ3TkZOL7x4k9x=4GRhrZ6Gm0W+Ai_UnX2FEg@mail.gmail.com> (raw)
In-Reply-To: <7v1umv7ub0.fsf@alter.siamese.dyndns.org>
On Mon, May 7, 2012 at 1:52 PM, Junio C Hamano <gitster@pobox.com> wrote:
> the
> shipping/logistics term "to stage" does not cleanly translate to the
> language without unnecessary connotation that imply what is described is
> something the our "index" actually is _not_.
I agree with Felipe that "staging" is the most appropriate term for
"adding to the index" in git. As a native English speaker, I have
never thought of "to stage" as relating to shipping in any way. To
me, by far the most common usage is in real estate. The seller of a
home "stages" it by setting up furniture and decorations to make the
home as appealing to prospective buyers as possible. Just search on
Google for "home staging" and you will get plenty of hits. This usage
clearly originates from theater but can be found in other contexts as
well.
next prev parent reply other threads:[~2012-05-19 0:51 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
2012-05-19 0:50 ` Mark Lodato [this message]
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='CAHREChgTHZL0sNJ3TkZOL7x4k9x=4GRhrZ6Gm0W+Ai_UnX2FEg@mail.gmail.com' \
--to=lodatom@gmail.com \
--cc=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).