git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	Christoph Reiter <reiter.christoph@gmail.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] add --interactive: allow `update` to stage deleted files
Date: Tue, 28 Jun 2022 19:08:03 -0400	[thread overview]
Message-ID: <YruJ06odaXmTOyjM@nand.local> (raw)
In-Reply-To: <xmqqr138h0wn.fsf@gitster.g>

On Tue, Jun 28, 2022 at 03:35:20PM -0700, Junio C Hamano wrote:
> The fix looks quite straight-forward.  It is somewhat disappointing
> that it was caught after this loooong time, but as they say, better
> late than never.

I had the same thought, but I think that it points to something I've
suspected privately for a while which is that we don't actually get many
users to opt-in to features early when they are hidden behind a
configuration.

I had hoped that things like feature.experimental would cause more users
to try features that weren't quite ready for prime-time more often, and
that we'd get more and better feedback as a result.

But I think that this proves that is generally not so. I think we
should probably err on the side of enabling new features by default so
long as there is sufficiently low risk, rather than hide them behind
config. Or at least, not hide them behind a config variable for so long
(though I am guilty of this myself with the pack.writeReverseIndex,
which I have been meaning to flip the default on for a little while
now).

In either case...

> Thanks for a quick report and a fix.

Yes, indeed. This fix looks good to me.


Thanks,
Taylor

  reply	other threads:[~2022-06-28 23:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 22:22 [PATCH] add --interactive: allow `update` to stage deleted files Johannes Schindelin via GitGitGadget
2022-06-28 22:35 ` Junio C Hamano
2022-06-28 23:08   ` Taylor Blau [this message]
2022-06-29 10:22     ` Ævar Arnfjörð Bjarmason

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=YruJ06odaXmTOyjM@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=johannes.schindelin@gmx.de \
    --cc=reiter.christoph@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).