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. .. Lana (lana.deere@xxxxxxxxx) On Fri, Sep 9, 2022 at 2:27 PM Junio C Hamano <gitster@xxxxxxxxx> wrote: > > Lana Deere <lana.deere@xxxxxxxxx> writes: > > > I can use a workaround to continue testing 2.37.2, but I saw in a > > different mail that there has already been a patch for this problem. > > I'm guessing that will be in 2.37.4. When would that be likely to be > > available? > > It is unlikely we would have 2.37.4 in the first place. > > The patch was already discussed and I expect it would take a few > more days before we agree it is a good approach to take, at which > time it will be merged to 'next'. And then it will be cooked for > about a week, before graduating to 'master', to be part of Git 2.38. > > Usually topics for fixing bugs are downmerged to 'maint' and lower > after they get merged and spent at least a week or so on the > 'master' branch. > > But by that time, the tip of the master branch would be already > tagged as 2.38-rc0 (see https://tinyurl.com/gitCal) and it is > unlikely that we would issue more maintenance releases for the 2.37 > track at that point, especially given that there are not that many > other topics to downmerge to 'maint' remaining on the master front. > > You can see when Git 2.38 is scheduled to become available from the > same calendar. > > Thanks.
