From: Jacob Keller <jacob.keller@gmail.com>
To: "David A. Wheeler" <dwheeler@dwheeler.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] doc: Modify git-add doc to say "staging area"
Date: Tue, 12 Dec 2017 21:40:12 -0800 [thread overview]
Message-ID: <CA+P7+xrWFE+6t-Z8cGQX5WtZP1_EQSa+J7vF65dLDSOnLfFxXQ@mail.gmail.com> (raw)
In-Reply-To: <E1eOwqn-0005Bd-OB@rmmprod05.runbox>
On Tue, Dec 12, 2017 at 6:32 PM, David A. Wheeler <dwheeler@dwheeler.com> wrote:
> Change the documentation of git-add so that it consistently uses
> the phrase "staging area". The current git documentation uses
> inconsistent terminology ("index", "cache", and "staging area").
> This commit switches git-add's documentation to consistently use
> the phrase "staging area", which is higher-level and should be less
> confusing for new users.
>
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.
Thanks,
Jake
next prev parent reply other threads:[~2017-12-13 5: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 [this message]
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
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=CA+P7+xrWFE+6t-Z8cGQX5WtZP1_EQSa+J7vF65dLDSOnLfFxXQ@mail.gmail.com \
--to=jacob.keller@gmail.com \
--cc=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
/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).