From: Junio C Hamano <gitster@pobox.com>
To: "David A. Wheeler" <dwheeler@dwheeler.com>
Cc: "Stefan Beller" <sbeller@google.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jacob Keller" <jacob.keller@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: [PATCH] doc: Modify git-add doc to say "staging area"
Date: Thu, 14 Dec 2017 11:40:51 -0800 [thread overview]
Message-ID: <xmqqfu8dt7wc.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <6382776C-175A-4E27-8D7C-385FFF167535@dwheeler.com> (David A. Wheeler's message of "Thu, 14 Dec 2017 14:05:21 -0500")
"David A. Wheeler" <dwheeler@dwheeler.com> writes:
> On December 14, 2017 1:50:00 PM EST, Junio C Hamano <gitster@pobox.com> wrote:
>>I agree with that. I do not consider the proposed change "good".
>
> Why is "index" better? It is a confusing name, one that has many
> other unrelated meanings. In particular, many projects managed by
> git also have an index, but few have a staging area.
That's an absurd argument. A database product that wants to be used
in library systems are forbidden to have "index" because that may be
confused with library index cards?
> Also, the phrase "staging area" is already in use, so this is not
> a new term (e.g., git-staging).
That gets us back to the "'X acts like Y' is different from 'X is
Y'".
Besides, the phrase "staging area" is a near-sighted and narrow
minded term. It focuses too much on working towards the next
commit, and ignores there are other aspects that are equally
important. When you check out historical revisions (without any
intention of making new commits, just sightseeing), for example, the
index does not act as "staging area" for creating a new commit. But
it still serves Git users by keeping track of the list of paths that
came from the HEAD, and recording their contents and the cached stat
info for the working tree files (all using the pathnames as keys
into these data items).
next prev parent reply other threads:[~2017-12-14 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 2:32 [PATCH] doc: Modify git-add doc to say "staging area" David A. Wheeler
2017-12-13 5:40 ` Jacob Keller
2017-12-13 5:46 ` David A. Wheeler
2017-12-13 12:54 ` Ævar Arnfjörð Bjarmason
2017-12-14 17:48 ` David A. Wheeler
2017-12-14 17:55 ` Ævar Arnfjörð Bjarmason
2017-12-14 18:08 ` Junio C Hamano
2017-12-14 18:24 ` Stefan Beller
2017-12-14 18:50 ` Junio C Hamano
2017-12-14 19:05 ` David A. Wheeler
2017-12-14 19:40 ` Junio C Hamano [this message]
[not found] ` <E1ePark-0008P4-Qx@rmmprod07.runbox>
2017-12-14 21:28 ` Stefan Beller
2017-12-14 19:41 ` Ævar Arnfjörð Bjarmason
2017-12-13 17:02 ` Junio C Hamano
2017-12-13 18:46 ` David A. Wheeler
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=xmqqfu8dt7wc.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.com \
--cc=sbeller@google.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).