git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Chris Howlett <chowlett09@gmail.com>
Cc: Chris Howlett via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	 Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Subject: Re: [PREVIEW v2] help: add prompt-yes setting for autocorrect
Date: Tue, 04 Mar 2025 14:33:44 -0800	[thread overview]
Message-ID: <xmqqzfi0mnnb.fsf@gitster.g> (raw)
In-Reply-To: <CAJVagJm36-Z8CtdDFgFXgQfmqGCD7i2rufoErGUc_ou2094How@mail.gmail.com> (Chris Howlett's message of "Tue, 4 Mar 2025 21:41:23 +0000")

Chris Howlett <chowlett09@gmail.com> writes:

> I've not seen any interaction with this patch since I posted it a
> couple of weeks ago. Has it slipped under the radar, or is there no
> interest in the change?

I personally do not find the cause so compelling, and am not myself
interested in a patch that pretty much has to duplicate the lines
needed to support existing AUTOCORRECT_PROMPT.  But others may feel
differently.

Around here, people do not react to everything they see, and some
may change their mind when asked the same question twice with some
interval in between, so it is a good idea to ping after some weeks
to reconfirm.

Thanks for pinging.

      reply	other threads:[~2025-03-04 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-15  9:36 [PATCH] help: add prompt-yes setting for autocorrect Chris Howlett via GitGitGadget
2025-01-15  9:51 ` Kristoffer Haugsbakk
2025-01-15 10:21   ` Chris Howlett
2025-01-15 17:40     ` Kristoffer Haugsbakk
2025-02-17 14:19 ` [PATCH v2] " Chris Howlett via GitGitGadget
     [not found] ` <pull.1852.v2.git.1739801702034.gitgitgadget@gmail.com>
2025-03-04 21:41   ` [PREVIEW " Chris Howlett
2025-03-04 22:33     ` 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=xmqqzfi0mnnb.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=chowlett09@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=kristofferhaugsbakk@fastmail.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).