On Wed, Jul 06, 2016 at 03:46:26PM +0100, Paul Jakma wrote:
> On Wed, 6 Jul 2016, Andrew Lunn wrote:
>
> >Are you planning on posting these patches to the list for review?
>
> Contributors generally post patches to the list (as is somewhat
> implied in HACKING.md, and explicit on the website). From there,
> they shouldn't need to do actively have to do anything, except
> respond to any emails if needs be (though, resending if nothing at
> all is heard for months would be a good idea).
Hi Paul
Thanks for the explanation. I'm used to the Linux kernel way of doing
things. Patches land in my mailbox, and if i find them interesting, or
are in an area of the kernel i'm familiarly with, i will often take
the time to hit reply and review the patch.
If it does not land in my mailbox, i will never see it, and never
review it. The kernel thinking seems to be that there are plenty of
people writing patches, but fewer reviewing patches. So make it easy
for the reviewer. Similarly, since there are more patch writers than
reviewers and mergers, it is the patch writers job to shepherd their
patch through the process. That helps with scalability.
Andrew
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
