On Fri, Jul 04, 2014 at 11:01:52AM +0200, Arnd Bergmann wrote:
On Thursday 03 July 2014 20:39:41 Olof Johansson wrote:
On Thu, Jul 3, 2014 at 5:39 PM, Kukjin Kim kgene.kim@samsung.com wrote:
Mark is the _only_ linux developer in the world who will give you crap for sending him patches to the very same email that he signs off all his work with.
I really wish Linaro would just let him sign off with his long-standing kernel.org email address instead so the rest of us wouldn't have to keep track of this.
Me too, it's a constant source of aggrivation.
FWIW David Miller has a similar policy: he only applies networking patches that are sent to the netdev mailing list. This seems like a good idea in general (to ensure they are getting exposed to the public).
Right, I do tend to insist on this as well (I also think some other patchwork users do this as well as davem, things need to hit the list to go into patchwork), plus including comaintainers where that's relevant. For the most part anything that ends up going to the work address also has one of those problems.
Mark, any chance we could convince to pick up patches from alsa-devel in the future even if they are sent to the wrong personal email account of yours? I would assume that would only require a small change in your filter rules, not a change in your workflow.
I do look at the lists but it's very easy for things that only go there to get missed and it's fairly low priority, the volume is very high and obviously there's a lot of duplication from things that do land in my inbox. Copying things into my inbox causes duplication problems due to things going to lkml, lakml and subsystem specific lists and alsa-devel being moderated for non-subscribers and subject mangling doesn't help anything.
What's more likely to happen is that I just start ignoring the work policy which is something I've been considering anyway.