Hi; does anybody else think it would be a good idea to move all the kernel patch email traffic off linaro-dev and onto a more kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev shows that something like 75% of it is kernel devs patchbombing the list. You don't see huge floods of patches here for gcc or QEMU or any of the many other projects Linaro contributes to, so why all the kernel patches?
I think that moving these off to their own list would allow those who have a genuine interest in kernel internals to read and review these patches, and reduce the noise level on this (Linaro's most generic list) for everybody else.
NB: I'm not suggesting "no kernel discussion here"; I just would like actual patchmail to go elsewhere...
thanks -- PMM
Since Peter and I were discussing this on IRC that led to this email, here is a bit of context on the current behaviour:
On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell peter.maydell@linaro.org wrote:
Hi; does anybody else think it would be a good idea to move all the kernel patch email traffic off linaro-dev and onto a more kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev shows that something like 75% of it is kernel devs patchbombing the list. You don't see huge floods of patches here for gcc or QEMU or any of the many other projects Linaro contributes to, so why all the kernel patches?
linaro-dev was supposed to be how we kept track of all development activity that Linaro was involved in - it wasn't supposed to be restricted only to kernel. IOW, someone could subscribe to this one list to find out everything that Linaro was participating in.
So much so that it was baked into our guidelines for how to use git to send patches to upstream projects[1]
Admittedly, those were early days and our contributions to upstream projects have grown significantly since then. So it might be time to revisit that policy.
I think that moving these off to their own list would allow those who have a genuine interest in kernel internals to read and review these patches, and reduce the noise level on this (Linaro's most generic list) for everybody else.
NB: I'm not suggesting "no kernel discussion here"; I just would like actual patchmail to go elsewhere...
thanks -- PMM
[1] https://wiki.linaro.org/Resources/HowTo/Git/GitSendEmail
On Mon, 18 Feb 2013, Amit Kucheria wrote:
Since Peter and I were discussing this on IRC that led to this email, here is a bit of context on the current behaviour:
On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell peter.maydell@linaro.org wrote:
Hi; does anybody else think it would be a good idea to move all the kernel patch email traffic off linaro-dev and onto a more kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev shows that something like 75% of it is kernel devs patchbombing the list. You don't see huge floods of patches here for gcc or QEMU or any of the many other projects Linaro contributes to, so why all the kernel patches?
linaro-dev was supposed to be how we kept track of all development activity that Linaro was involved in - it wasn't supposed to be restricted only to kernel. IOW, someone could subscribe to this one list to find out everything that Linaro was participating in.
So much so that it was baked into our guidelines for how to use git to send patches to upstream projects[1]
Admittedly, those were early days and our contributions to upstream projects have grown significantly since then. So it might be time to revisit that policy.
I think that moving these off to their own list would allow those who have a genuine interest in kernel internals to read and review these patches, and reduce the noise level on this (Linaro's most generic list) for everybody else.
NB: I'm not suggesting "no kernel discussion here"; I just would like actual patchmail to go elsewhere...
For the record, I think what Peter is suggesting is reasonable. There must be better ways for people to find out what Linaro is participating in other than scaring them away from linaro-dev when they have no interest in the patch details.
Nicolas
On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
On Mon, 18 Feb 2013, Amit Kucheria wrote:
Since Peter and I were discussing this on IRC that led to this email, here is a bit of context on the current behaviour:
On Mon, Feb 18, 2013 at 8:16 PM, Peter Maydell peter.maydell@linaro.org wrote:
Hi; does anybody else think it would be a good idea to move all the kernel patch email traffic off linaro-dev and onto a more kernel-specific mailing list (eg, linaro-kernel, maybe) ?
A quick eyeball of a few pages of my gmail folder for linaro-dev shows that something like 75% of it is kernel devs patchbombing the list. You don't see huge floods of patches here for gcc or QEMU or any of the many other projects Linaro contributes to, so why all the kernel patches?
linaro-dev was supposed to be how we kept track of all development activity that Linaro was involved in - it wasn't supposed to be restricted only to kernel. IOW, someone could subscribe to this one list to find out everything that Linaro was participating in.
So much so that it was baked into our guidelines for how to use git to send patches to upstream projects[1]
Admittedly, those were early days and our contributions to upstream projects have grown significantly since then. So it might be time to revisit that policy.
I think that moving these off to their own list would allow those who have a genuine interest in kernel internals to read and review these patches, and reduce the noise level on this (Linaro's most generic list) for everybody else.
NB: I'm not suggesting "no kernel discussion here"; I just would like actual patchmail to go elsewhere...
For the record, I think what Peter is suggesting is reasonable. There must be better ways for people to find out what Linaro is participating in other than scaring them away from linaro-dev when they have no interest in the patch details.
I second that.
Nicolas
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 18 February 2013 23:50, Serge Broslavsky serge.broslavsky@linaro.org wrote:
On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
For the record, I think what Peter is suggesting is reasonable. There must be better ways for people to find out what Linaro is participating in other than scaring them away from linaro-dev when they have no interest in the patch details.
I second that.
Any consensus on this? I have already stated mailing to people (who send their patches to linaro-dev) to use linaro-kernel. :)
On Thu, Feb 21, 2013 at 4:27 PM, Viresh Kumar viresh.kumar@linaro.org wrote:
On 18 February 2013 23:50, Serge Broslavsky serge.broslavsky@linaro.org wrote:
On 18.02.13 12:20 -0500, Nicolas Pitre wrote:
For the record, I think what Peter is suggesting is reasonable. There must be better ways for people to find out what Linaro is participating in other than scaring them away from linaro-dev when they have no interest in the patch details.
I second that.
Any consensus on this? I have already stated mailing to people (who send their patches to linaro-dev) to use linaro-kernel. :)
I don't have a strong preference one way or another about switching from linaro-dev to linaro-kernel.
Don't forget to update https://wiki.linaro.org/Resources/HowTo/Git/GitSendEmail
/Amit
On 21 February 2013 16:34, Amit Kucheria amit.kucheria@linaro.org wrote:
I don't have a strong preference one way or another about switching from linaro-dev to linaro-kernel.
Don't forget to update https://wiki.linaro.org/Resources/HowTo/Git/GitSendEmail
Done.
-
Amit Kucheria -
Nicolas Pitre -
Peter Maydell -
Serge Broslavsky -
Viresh Kumar