git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jacek Lipiec <jacek.lipiec.bc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Multiple indices / staging areas
Date: Fri, 02 Feb 2024 00:35:59 -0800	[thread overview]
Message-ID: <xmqqr0hvuuts.fsf@gitster.g> (raw)
In-Reply-To: <CAPGWkwcqbkanFP4h1P0umJAFzmiQYTvSm1KeD0=yY0n2K=KS7g@mail.gmail.com> (Jacek Lipiec's message of "Tue, 30 Jan 2024 04:47:27 +0100")

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.

      reply	other threads:[~2024-02-02  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  3:47 Multiple indices / staging areas Jacek Lipiec
2024-02-02  8:35 ` Junio C Hamano [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqr0hvuuts.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jacek.lipiec.bc@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.
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 NNTP newsgroup(s).