On Thu, 26 Mar 2020 15:40:47 +0100 (CET) Johannes Schindelin wrote: JS> On Thu, 26 Mar 2020, Vadim Zeitlin wrote: JS> JS> > On Wed, 25 Mar 2020 20:04:09 +0100 Johannes Schindelin wrote: [...] JS> > JS> That rationale makes sense to me, as does the patch. JS> > JS> > Sorry for a possibly stupid question, but what is the next thing to do JS> > now? The instructions in Documentation/SubmittingPatches indicate that I JS> > should wait until the "list forms consensus that [...] your patch is good", JS> > but it's not quite clear what indicates that a consensus has been reached. JS> > Is your comment above enough or should I wait for something else? And JS> > if/when it has been reached, do I really I need to resend the patch to JS> > the maintainer and cc the list as written in that document? I'm a bit JS> > surprised by this because I don't see (most) patches being resent to this JS> > list. JS> JS> My take is that this was waiting for a review, and I provided it (*not* JS> asking for any changes), and if there are no further reviews, the patch JS> should make it into the `pu` branch, then `next` and eventually `master`, JS> at which point it will be slated for the next official `.0` version. JS> JS> It might make sense to ask for it to be trickled down into the `maint` JS> branch, too, in case a `v2.26.1` is released. I would be in favor of that, JS> but would not do the asking myself ;-) Hello again, Sorry to nag, but I'd like to return to this patch[*] because it looks like it could have fallen through the cracks: there didn't seem to be any more comments about it, except for Johannes' positive review, but it didn't get mentioned in any "What's cooking" threads since then neither. [*] https://public-inbox.org/git/20200319010321.18614-1-vz-git@zeitlins.org/ So I'd just like to ask directly, hoping that it's not inappropriate: Junio, do I need to do anything to get this patch accepted or am I just being too impatient? Thanks in advance, VZ