Hi Junio, On Sat, 3 Jun 2017, Junio C Hamano wrote:
> Johannes Schindelin <[email protected]> writes: > > > On Fri, 2 Jun 2017, Junio C Hamano wrote: > > > >> Samuel Lijin <[email protected]> writes: > >> > >> >> What is holding this topic up? Anything Ben or I can do to move this > >> >> closer to `next` or even `master`? > >> > > >> > It's in `next` right now (3196d093d6). > >> > >> Thanks for pinging and checking ;-) > >> > >> I think the topic was merged to 'next' on the 23rd of last month and > >> graduated to 'master' in the past few days, together with other > >> topics. > > > > Okay. I never saw any "Will merge to" message, so I got worried. > > Well, I cannot quite help if you are not reading them ;-) Well, I cannot quite help when I am expected to read long "What's cooking" mails with out-of-context information as opposed to replies to the threads discussing the actual patch series. :-P I understand that it would be hard on you if I expected you to untangle your What's cooking discussions into the mail threads with the corresponding patches, of course. That just proves my point about mailing lists being an inadequate means to perform code review... > Issue #06 of May marked it to be merged to 'next': > https://public-inbox.org/git/<[email protected]> > > Issue #07 of May marked it for 'master': > https://public-inbox.org/git/<[email protected]> > > Issue #08 of May kept it (i.e. no issues discovered in the > meantime): > https://public-inbox.org/git/<[email protected]> > > Issue #01 of June reports it in 'master': > https://public-inbox.org/git/<[email protected]> Thank you, Dscho
