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
