Junio C Hamano <gitster@xxxxxxxxx> writes: > Phillip Wood <phillip.wood123@xxxxxxxxx> writes: > >> On 12/01/2020 16:12, Phillip Wood wrote: >>> I'm concerned that there are some bugs in this series and think >>> it may be best to revert it before releasing 2.25.0. > > Let's do that. > ... >>> J > > In any case, the tip of 'master' (hence the one that would become > the final) is simpler to remedy by just reverting the merge, but > there are a handful of in-flight topics that may have been queued by > forking 'master' after the problematic merge was made (iow, anything > after the fifth batch for this cycle), which I'd have to be a bit > careful when I merge them down, lest they attempt to pull in the bad > topic again. But that will be something we need to worry about > after the release, not before the final. I will push out what I wish to be able to tag as the final [*1*] shortly but without actually tagging, so that it can get a bit wider exposure than just the usual "Gitster tested locally and then did let Travis try them" testing. Thanks. [Reference] *1* The tip of 'master' as of this writing is v2.25.0-rc2-24-gb4615e40a8
