git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] doc: Modify git-add doc to say "staging area"

From
Stefan Beller <sbeller@google.com>
Date
Dec 14, 2017, 18:24 UTC
Message-ID
<CAGZ79kZeMVLesunBzW5hhN-snL8fBXdjPgy=Tt8JCDmhDePDZA@mail.gmail.com>
In-Reply-To
<xmqq6099uqq9.fsf@gitster.mtv.corp.google.com>
On Thu, Dec 14, 2017 at 10:08 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 16 quoted lines
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
>> On Wed, Dec 13, 2017 at 6:46 AM, David A. Wheeler <dwheeler@dwheeler.com> wrote:
>>> 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).
>>
>> After your patch the majority of the docs will still talk about
>> "index", is this part of some larger series, perhaps it would be good
>> to see it all at once...
>
> ... or none of it.  I do not quite see a point of spending list
> bandwidth on a change like this one.

I think wording (as well as its consistency) in the documentation is rather important.

Just the other day I was reading[1], yet another blog explaining
why git sucks. TL;DR:
(1) (a) The staging area is an advanced concept
    and should be disabled by default
    (b) and is documented super confusingly.
(2) Branches and Remotes Management is
    Complex and Time-Consuming
(3) its ecosystem (GitHub et al.) is not pushing for
    innovation, because "forks are not the right model".
[1] https://gregoryszorc.com/blog/2017/12/11/high-level-problems-with-git-and-how-to-fix-them/

When I saw the original patch, I assumed it was a reaction to this blog and attempting to fix (1b), but maybe it is unrelated.

Anyway I think spending list band width on good documentation is not bandwidth wasted.

Stefan
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 15 in “doc: Modify git-add doc to say "staging area"”
  1. doc: Modify git-add doc to say "staging area"David A. Wheeler, Dec 13, 2017
  2. Jacob KellerDec 13, 2017
  3. David A. WheelerDec 13, 2017
  4. Ævar Arnfjörð BjarmasonDec 13, 2017
  5. David A. WheelerDec 14, 2017
  6. Ævar Arnfjörð BjarmasonDec 14, 2017
  7. Junio C HamanoDec 14, 2017
  8. Stefan BellerDec 14, 2017
  9. Junio C HamanoDec 14, 2017
  10. David A. WheelerDec 14, 2017
  11. Junio C HamanoDec 14, 2017
  12. Ævar Arnfjörð BjarmasonDec 14, 2017
  13. Junio C HamanoDec 13, 2017
  14. David A. WheelerDec 13, 2017
  15. Stefan BellerDec 14, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.