On 19/11/2021 19:28, Junio C Hamano wrote: > Philip Oakley <philipoakley@iee.email> writes: > >>>> My patches are in https://github.com/PhilipOakley/git/tree/oneU_t >>> How about rebasing the remaining patches from >>> https://github.com/git-for-windows/git/compare/main...PhilipOakley:oneU_t >>> on top of `rs/mergesort` and then submitting them, to avoid duplicate >>> efforts? >>> >> I'm not finding a `rs/mergesort` at the moment. Any particular remote I >> should find it on, or maybe a different spelling? >> P. > At https://github.com/gitster/git/, I publish the "broken out" > branches. > > But resurrecting the tips of the topics should be fairly easy. > > $ git log --first-parent --oneline origin/master..origin/seen | > grep rs/mergesort > > The second parent of that merge is the tip of rs/mergesort topic > back when the 'seen' integration branch was created. > Thanks. I'd been browsing via `gitk` and hadn't included all the tips, so couldn't find it at that point. I've got it now: 42c456ff81 (mergesort: avoid left shift overflow, 2021-11-16). Philip
