Hi Junio, On Sun, 18 Dec 2022, Junio C Hamano wrote: > * pg/diff-stat-unmerged-regression-fix (2022-12-15) 1 commit > (merged to 'next' on 2022-12-16 at 2a61376847) > + diff: fix regression with --stat and unmerged file > > The output from "git diff --stat" on an unmerged path lost the > terminating LF in Git 2.39, which has been corrected. > > Will merge to 'master'. > source: <20221214174150.404821-1-pete@xxxxxxxxxxxxx> This probably should go to `maint` soon-ish, as it is a 2.39.0 regression, right? Speaking of regressions, there is also the bundle regression fix at https://lore.kernel.org/git/patch-1.1-2319eb2ddbd-20221220T133941Z-avarab@xxxxxxxxx/ and the not-quite-ready p4 bug fix at https://lore.kernel.org/git/CAKu1iLWvd+PVOK405Q+SNDyyYnhbi=LtovZvWw55y6eQqoRpaA@xxxxxxxxxxxxxx/ Are there more regressions that would maybe merit a v2.39.1? How imminent do you think Git v2.39.1 is? I ask because I'll most likely have to prepare a Git for Windows release before the holidays for a couple of regressions in components that have been fixed in the meantime, and naturally I would like to avoid releasing Git for Windows v2.39.0(2) only to release Git for Windows v2.39.1 a few days later. Ciao, Johannes
