On Mon, Sep 12, 2022 at 10:58:53AM -0400, Lana Deere wrote: > Thanks for the info. That sounds kind of like this fix, even if > accepted, would miss rc0 but would be not unlikely to make rc1. Is > there any way to "watch" the issue so I can know which git release > gets the fix? I would like to be an early adopter of that release > since I would want to test the change works for me. Thanks. Early testing, especially of release candidates, is very welcome. There's no tracking for a specific issue, but you can check the status of the commit. The fix has been merged to 'next' now, so the commit id will remain stable. You can periodically fetch any of the usual Git mirrors[1] and check: git tag --contains 49ca2fba393fa277ab70253337c53c7831597c3a Likewise, you can see when it hits master with "git branch -a --contains". You can also see the progress of topics in Junio's "What's cooking" emails. If you're not a regular list reader, you can hit the recent ones here: https://lore.kernel.org/git/?q=f%3Ajunio+s%3Acooking Likewise, when -rc0, etc, are released, the release notes should mention (or not) this fix. You can see those announcements in the archive like this: https://lore.kernel.org/git/?q=f%3Ajunio+t%3Avger+s%3Aannounce -Peff [1] e.g., https://git.kernel.org/pub/scm/git/git.git/
