From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Chris Howlett" <chowlett09@gmail.com>
Cc: "Josh Soref" <gitgitgadget@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] help: add prompt-yes setting for autocorrect
Date: Wed, 15 Jan 2025 18:40:45 +0100 [thread overview]
Message-ID: <4a396e63-5e82-4ce4-83c2-13d508cb1f7f@app.fastmail.com> (raw)
In-Reply-To: <CAJVagJ=3uxcCpEivkpW5_HTxdL9Sa9Ymqm1iJQHUJ+=9XneLSg@mail.gmail.com>
On Wed, Jan 15, 2025, at 11:21, Chris Howlett wrote:
> On Wed, 15 Jan 2025 at 09:51, Kristoffer Haugsbakk
> > [snip]
>
> That's unsurprising, as I was inspired to add this option after
> reading that committer's blog post on help.autocorrect -
> https://blog.gitbutler.com/why-is-git-autocorrect-too-fast-for-formula-one-drivers/
>
> I'm happy to wait for their patch to be merged, then rebase and rework
> against it, if that seems the most sensible option? Presumably I'll
> have to monitor the mailing list to learn when that happens? This is
> my first patch to git, so I'm not sure of process.
You can keep an eye on the “What's cooking” emails.[1] The latest
one mentions this other topic as branch `sc/help-autocorrect-one`
(that’s Scott Chacon’s initals followed by the topic name).
If you want to wait for that one to get merged:
• Wait until you see such an email with this “status” under it:
Will merge to 'master'.
Which means that it will be merged to `master` soon.
(Or maybe run
git branch --remote --contains=origin/sc/help-autocorrect-one \
| grep master
from time to time (I don’t know, I’ve never had to do that).)
Or else you could build on top of it. That’s more advanced though.
Not something I’ve done myself.[2]
† 1: Latest: https://lore.kernel.org/git/xmqqzfjt2qye.fsf@gitster.g/
† 2: See `Documentation/SubmittingPatches under “select few topic
branches that are” for how to depend on in-flight topics
next prev parent reply other threads:[~2025-01-15 17:41 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 [this message]
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
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=4a396e63-5e82-4ce4-83c2-13d508cb1f7f@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=chowlett09@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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).