Hi Junio, On Thu, 24 Aug 2017, Junio C Hamano wrote:
> Lars Schneider <larsxschnei...@gmail.com> writes: > > > On 22 Aug 2017, at 21:56, Junio C Hamano <gits...@pobox.com> wrote: > > > >> Here are the topics that have been cooking. Commits prefixed with > >> '-' are only in 'pu' (proposed updates) while commits prefixed with > >> '+' are in 'next'. The ones marked with '.' do not appear in any of > >> the integration branches, but I am still holding onto them. > >> > >> The second batch of topics are in. This cycle is going a bit slower > >> than the previous one (as of mid-week #3 of this cycle, we have > >> about 200 patches on 'master' since v2.14, compared to about 300 > >> patches in the cycle towards v2.14 at a similar point in the cycle), > >> but hopefully we can catch up eventually. > >> > >> I am planning to be offline most of the next week, by the way. > >> > >> You can find the changes described here in the integration branches > >> of the repositories listed at > >> > >> http://git-blame.blogspot.com/p/git-public-repositories.html > >> > >> -------------------------------------------------- > >> [Graduated to "master"] > >> > > > > Hi Junio, > > > > just in case this got lost: I posted a patch with an improvement to > > 2841e8f ("convert: add "status=delayed" to filter process protocol", > > 2017-06-30) which was merged to master in the beginning of 2.15. > > > > https://public-inbox.org/git/20170820154720.32259-1-larsxschnei...@gmail.com/ > > Thanks for pinging, but next time ping the thread itself if it is > about something that is not in What's cooking report you are > responding to. If you want *contributors* to ping the thread themselves, how about *posting your updates there, too*? It does make things inconvenient for contributors if they have to monitor those Whats' cooking emails in addition to the mail threads, you know? Ciao, Dscho
