git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: Jacob Keller <jacob.keller@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] doc: Modify git-add doc to say "staging area"
Date: Wed, 13 Dec 2017 00:46:12 -0500	[thread overview]
Message-ID: <01075529-4B7B-4C05-927F-0504315F2B3F@dwheeler.com> (raw)
In-Reply-To: <CA+P7+xrWFE+6t-Z8cGQX5WtZP1_EQSa+J7vF65dLDSOnLfFxXQ@mail.gmail.com>

On December 13, 2017 12:40:12 AM EST, Jacob Keller <jacob.keller@gmail.com> wrote:
>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".

I think "staging area" is the better term. It focuses on its purpose, and it is also less confusing ("index" and "cache" have other meanings in many of the repos managed by git).


--- David A.Wheeler

  reply	other threads:[~2017-12-13  5:46 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 [this message]
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
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=01075529-4B7B-4C05-927F-0504315F2B3F@dwheeler.com \
    --to=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).