git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Philip Oakley" <philipoakley@iee.org>
To: "Felipe Contreras" <felipe.contreras@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
	"Junio C Hamano" <gitster@pobox.com>,
	"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>,
	"Matthieu Moy" <matthieu.moy@imag.fr>,
	"Piotr Krukowiecki" <piotr.krukowiecki.news@gmail.com>
Subject: Re: [1.8.0] use 'stage' term consistently
Date: Sat, 5 May 2012 20:53:36 +0100	[thread overview]
Message-ID: <38B7BCC61E844EAD97CC18D5D7299DD5@PhilipOakley> (raw)
In-Reply-To: CAMP44s1isa2a=a-QLGaE9ThW1iUBj0je2NUi8FVxqA=OELLmyA@mail.gmail.com

From: "Felipe Contreras" <felipe.contreras@gmail.com> Sent: Saturday, May
05, 2012 6:30 PM
> On Sat, May 5, 2012 at 6:52 PM, Philip Oakley <philipoakley@iee.org>
> wrote:
>> From: "Felipe Contreras" <felipe.contreras@gmail.com> Sent: Saturday, May
>> 05, 2012 2:04 PM
>>
>>> Proposal:
>>>
>>> Avoid the terms 'cache' and 'index' in favor of 'stage'.
>>>
>>> Advantages:
>>>
>>> The term 'stage' is more intuitive for newcomers which are more
>>> familiar with English than with git, and it seems to be a
>>> straightforward mental notion for people from different mother
>>> tongues.
>>>
>>> It is so intuitive that it is used already in a lot online
>>> documentation, and the people that do teach git professionally use
>>> this term.
>>
>>
>> I've never found any of the terms to be great (as per this discussion
>> ;-).
>>
>> The term that helped me most, heard on one of the git videos, was "it's
>> like
>> a manifest", alluding to a 'shipping manifest', which then leads to both
>> the
>> "staging area" and "index" terms. Though "index" is probably too
>> technical
>> for most folk.
>>
>> The allusion to shipping a consignment or rail marshalling
>> (classification)
>> yards, and similar freight flows
>
> Perhaps, but these terms are not already used everywhere, unlike
> 'stage', and haven't been brought in past discussions. Personally the
> word 'manifest' says nothing to me (manifesto?), neither does
> consignment, or marshalling.

Useful to know..  The fact that there is such a variety of terms, usually
based on specialist transport, is an indication of our on-going
difficulties - people just don't talk about this aspect of 'work'. Usually
it (packaging)  is 'someone else's problem' ;-)  E.g. what's it called when
the post office batches up mail in the 'sorting' office? - I don't know, nor 
usually care, except when I just post 60 letters to Hawaii - should I put a 
band around them to 'help' the post office ... In the git case, unusually 
for a VCS, we do our own grouping, but need a verb.

Aside: wikipedia notes that even UK and US English railways can't agree 
their term
(http://en.wikipedia.org/wiki/Marshalling_yards) on what to call the
'staging' process we are discussing

I looked up a translation (I hope I haven't mis-chosen):
    shipping manifest (n) (bill or inventory enclosed with a consignment)
    manifiesto de carga (nm)
so (to me) it does look like "index" is the best word for our *list* of what 
we have
prepared, and the stage of preparation of those items for our next commit 
(shipment to the repo).

It probably doesn't help that the concepts and the implementation aren't 
always in alignment (a generic DVCS problem). e.g. when we `add` a file, a 
copy goes straight into our objects store, but isn't actually 'in' the repo. 
So the discussion suffers from knowing too much.

> As discussed before, we need a term that
> has a nice noun (stage), verb (to stage), and past-participle
> (staged). There have been a lot of suggestions, but nothing as good as
> 'stage', which is presumably the reason why it's so prevalent in
> online documentation.

Ooops, my note about my wording suggestions being used for *explanation* got 
lost in
the trimming. I wasn't suggesting a change to the candidate terms.

>
> Maybe you are quite familiar with ships :)
>
UK - home of the railways, and the SS Great Britain, and the Titanic ...
Philip 

  reply	other threads:[~2012-05-05 19:53 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 [this message]
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
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=38B7BCC61E844EAD97CC18D5D7299DD5@PhilipOakley \
    --to=philipoakley@iee.org \
    --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=matthieu.moy@imag.fr \
    --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).