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

Re: Multiple indices / staging areas

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 2, 2024, 08:35 UTC
Message-ID
<xmqqr0hvuuts.fsf@gitster.g>
In-Reply-To
<CAPGWkwcqbkanFP4h1P0umJAFzmiQYTvSm1KeD0=yY0n2K=KS7g@mail.gmail.com>
Jacek Lipiec <jacek.lipiec.bc@gmail.com> writes:
> I am open for the feedback/questions, or early go/nogo.

Given that even having one index between the committed history and the working tree files seems to add cognitive load to new users, I am not very enthused to hear that we may be able to add an arbitrary number of them, and more importantly, I don't quite see what real world problems the additional complexities (most of them are probably not accounted for in the sketch we saw and yet to be discovered) are solving.

But I'll wait before sending this response for a few days and keep it in my outbox.

Previous: Jacek Lipiec
Message 2 of 2 in “Multiple indices / staging areas”
  1. Jacek LipiecJan 30, 2024
  2. Junio C HamanoFeb 2, 2024

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.