-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, We've had a very strict patch review regime since we moved over to git. We see that this regime does work, but it can take a very long time before patches are reviewed and ACKed for inclusion. This long delay is something we are less happy about. So I'm suggesting a new approach here. I've noticed that if there are issues with patches, they are usually NACKed rather fast. But the explicit ACKs are not happening as fast. And this is something I'd like to make take an advantage of. I'm suggesting that if there are patches which someone do find useful, which has not been accepted, they need to be ACKed. But if I see that a patch is floating on the ML longer than 14 days without any responses and I on a cursory glance see that this patch can make some sense, I will apply this patch to the git tree. These patches will not have any 'Acked-by' statement. If I see that a patch is relevant and want a second opinion about it, I will nag some concrete persons. If they don't respond after 14 days, I will most likely add the patch, adding a 'Cc:' statement with their mail address. This is to indicate in the commit log that the Cc'ed persons have been informed about this patch. If it turns out that a patch should not have been included, we will naturally revert the patch again, provided we get a reasonable explanation why it needs to be reverted. This is only a suggestion, but unless this causes a clear dissatisfaction in the community, I'd like to start using this new outline asap. kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7Yx0EACgkQDC186MBRfrrBLgCfe07JKnrHEzqCVUsWcN/8QiEF 77YAnjcF5roFXK4jY9qI9mlBdJpXOygF =lsbW -----END PGP SIGNATURE-----
