On Tue, Aug 19, 2025 at 5:37 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > <rsbecker@xxxxxxxxxxxxx> writes: > > > On August 19, 2025 4:46 PM, Junio C Hamano wrote: > >>Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> > >>--- > >> GIT-VERSION-GEN | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >>diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN index > >>be801415bddc..64cbc5833536 100755 > >>--- a/GIT-VERSION-GEN > >>+++ b/GIT-VERSION-GEN > >>@@ -1,6 +1,6 @@ > >> #!/bin/sh > >> > >>-DEF_VER=v2.51.0-rc2 > >>+DEF_VER=v2.51.0 > >> > >> LF=' > >> ' > > > > Will this cause a re-roll of the git 2.51.0 release? > > I don't know. This is not something I did. I also don't see any such PRs at GitGitGadget: https://github.com/gitgitgadget/git/pulls?q=2.51.0 But when triple-checking the lore archive, I realized that I think this is a result of Julia's PR getting rebased on top of 2.51.0? https://github.com/gitgitgadget/git/pull/1952/commits Perhaps Julia didn't use `--keep-base`, which I often forget to do when rebasing for contribution to Git (it's common in my other projects to omit it when working on the next version of a series). Indeed, fetching the published branch shows it's sitting on top of the v2.51.0 tag. -- D. Ben Knoble
