On Thu, 7 Jul 2016, David Lamparter wrote:
Because *everyone* can convert old patchwork patches into current mails by simply remailing them.
Though, that need not be helpful.
I really feel like we just need to get the ball rolling... on stuff that's *currently* coming in.
So start the collation phase for another round on top off 'ff'. Update the status in patchwork, and add a bundle. Send out the email to notify contributors of the status. Merge them into a linear history. Invite reviews, find the nits, fix and/or pushback stuff that needs fixing.
Or do it on a per-patch basis, if you don't like batching (certain things in getting through patches will inherently require serialisation, if there are multiple integrators active - batching can lower overheads on that, but hey).
AFAIK, you can't integrate stuff quickly, and review it, and have a history that is nice for others to base work on or pick from, and have stability.
There are no magic ponies. Not even in projects with equine themed names.
regards, -- Paul Jakma | [email protected] | @pjakma | Key ID: 0xD86BF79464A2FF6A Fortune: The worst thing about some men is that when they are not drunk they are sober. -- William Butler Yeats _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
