git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: "David A. Wheeler" <dwheeler@dwheeler.com>, git <git@vger.kernel.org>
Subject: Re: [PATCH] doc: Modify git-add doc to say "staging area"
Date: Wed, 13 Dec 2017 09:02:42 -0800	[thread overview]
Message-ID: <xmqq8te6y30t.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA+P7+xrWFE+6t-Z8cGQX5WtZP1_EQSa+J7vF65dLDSOnLfFxXQ@mail.gmail.com> (Jacob Keller's message of "Tue, 12 Dec 2017 21:40:12 -0800")

Jacob Keller <jacob.keller@gmail.com> writes:

> I know we've used various terms for this concept across a lot of the
> documentation. However, I was under the impression that we most
> explicitly used "index" rather than "staging area".
>
> Additionally, I think there are many other locations which
> consistently use "index" as the term already.

Another reason why we would want to standardize in the other
direction is because "X acts as Y" does not mean "X is Y".

It is true that we (and also "newbie friendly" tutorials) often
explain the index like so: "When working towards the next commit,
you improve the contents a bit in the working tree, you 'git add' it
to the index to make the contents of the index closer to what you
want to have the next commit.  The index works like the staging
area."

But that is not the only thing the index does.  When "git merge"
finds conflicting changes, it adds the contents for common, our and
their variants to the index for the path.  This is quite different
from how you use the index "as staging area"; the index is being
used as the "merging area".  When "git clean" wants to see which
paths it finds on the filesystem are not of interest, it consults
the index, which acts as the list of paths that are of interest.

  parent reply	other threads:[~2017-12-13 17:02 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
     [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 [this message]
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=xmqq8te6y30t.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dwheeler@dwheeler.com \
    --cc=git@vger.kernel.org \
    --cc=jacob.keller@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).