Nipunn Koorapati <nipunn1313@xxxxxxxxx> writes: >> Eventually by backporting, but a fix typically goes to the current >> development track first so it would happen after 2.30 is finished, I >> would think. > > I wanted to bump this idea - now that it appears that 2.30 is complete > and the new maint branch. Given that this patch makes matching-refspec > unusable in 2.29, would it make sense to backport a fix to the 2.29 > release? Yes, it does make sense. If we were to spend engineering effort to cut a 2.29.1, however, we'd better make sure not just this fix but all the other fixes relevant to the 2.29 track that are already well tested are included in it. We just issued 2.30 and not many people are using it to exercise a relatively new negative pathspec feature yet, so it probably is a good idea to spend a weeks or two to enumerate what other things we want to be in the 2.29 maintenance track. I personally do not have time for doing that myself right now, but luckily it is something contributors like you can step in to help ;-) Thanks.
