From: Felipe Contreras <felipe.contreras@gmail.com>
To: Karsten Blees <karsten.blees@gmail.com>,
Philip Oakley <philipoakley@iee.org>,
Felipe Contreras <felipe.contreras@gmail.com>,
Git List <git@vger.kernel.org>
Cc: Piotr Krukowiecki <piotr.krukowiecki.news@gmail.com>,
Jay Soffian <jaysoffian@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
William Swanson <swansontec@gmail.com>,
Ping Yin <pkufranky@gmail.com>,
Hilco Wijbenga <hilco.wijbenga@gmail.com>,
Miles Bader <miles@gnu.org>
Subject: Re: [PATCH v2 00/14] Officially start moving to the term 'staging area'
Date: Thu, 24 Oct 2013 18:19:48 -0500 [thread overview]
Message-ID: <5269ab14157b8_6704135de7c73@nysa.notmuch> (raw)
In-Reply-To: <5268706B.4040303@gmail.com>
Karsten Blees wrote:
> (2) Index
>
> An index, as in a library, maps almost perfectly to what the git index is
> _and_ what we do with it.
Not really. An index in the context of a library, and in any other context, is
a tool that indicates where something is, in order to find it quickly.
That is not how the Git index is used, nor what it is.
> (3b) Staging area (other meanings)
>
> I don't see how a stage (as in a theater) is in any way related to the git
> index.
>
> Data staging (as in loading a datawarehouse or web-server) fits to some
> extent, as its also about copying information, not moving physical things.
A stage in theater, and in any other context, is a special place, a standing
place, I don't see what is so different from the git staging area.
> > Even 'native' speakers don't have a single consistent term for the
> > concept. Terms are stolen from many varied industries and activities
> > that have to prepare and package items (Ships, Trains, Theaters)
> > (see http://en.wikipedia.org/wiki/Shipping_list, for a shortish list, which doesn't mention an Index)
>
> All true, but we don't need to steal terms from unrelated fields if
> information science provides us with the terms we need.
But it doesn't.
--
Felipe Contreras
next prev parent reply other threads:[~2013-10-25 4:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 22:29 [PATCH v2 14/14] completion: update 'git reset' new stage options Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 04/14] grep: add --staged option Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 07/14] stash: add --stage to pop and apply Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 00/14] Officially start moving to the term 'staging area' Felipe Contreras
2013-10-14 22:51 ` Felipe Contreras
2013-10-17 19:50 ` Junio C Hamano
2013-10-17 21:50 ` Felipe Contreras
2013-10-18 9:46 ` Matthieu Moy
2013-10-18 10:26 ` John Szakmeister
2013-10-18 10:36 ` Felipe Contreras
2013-10-18 11:38 ` Max Horn
2013-10-18 23:28 ` Karsten Blees
2013-10-19 0:41 ` Felipe Contreras
2013-10-19 14:08 ` Philip Oakley
2013-10-24 0:57 ` Karsten Blees
2013-10-24 8:32 ` Andreas Krey
2013-10-24 23:19 ` Felipe Contreras [this message]
2013-10-14 22:29 ` [PATCH v2 10/14] apply: add --work, --no-work options Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 01/14] Add proper 'stage' command Felipe Contreras
2013-10-14 23:06 ` Eric Sunshine
2013-10-14 23:15 ` Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 09/14] apply: add --stage option Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 03/14] diff: document --staged Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 05/14] rm: add --staged option Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 02/14] stage: add edit command Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 13/14] reset: allow --keep with --stage Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 12/14] reset: add --stage and --work options Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 08/14] submodule: add --staged options Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 11/14] completion: update " Felipe Contreras
2013-10-14 22:29 ` [PATCH v2 06/14] stash: add --stage option to save Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5269ab14157b8_6704135de7c73@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=hilco.wijbenga@gmail.com \
--cc=jaysoffian@gmail.com \
--cc=jrnieder@gmail.com \
--cc=karsten.blees@gmail.com \
--cc=miles@gnu.org \
--cc=philipoakley@iee.org \
--cc=piotr.krukowiecki.news@gmail.com \
--cc=pkufranky@gmail.com \
--cc=swansontec@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).