Re: [Ksummit-discuss] [MAINTAINER SUMMIT] community management/subsystem governance

[Daniel Vetter <daniel.vetter@ffwll.ch>]

On Tue, Sep 11, 2018 at 12:09 PM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> On Tue, Sep 11, 2018 at 12:01 PM Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>> On Tue, Sep 11, 2018 at 11:08 AM, Geert Uytterhoeven
>> <geert@linux-m68k.org> wrote:
>> > On Tue, Sep 11, 2018 at 10:44 AM Jani Nikula <jani.nikula@intel.com> wrote:
>> >> On Mon, 10 Sep 2018, Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
>> >> > That's also one of my concerns. The differences between subsystems that all
>> >> > use an email-based review process can already be confusing, or just annoying
>> >> > to handle, especially when specific tools are mandated (the DRM dim tool or
>> >> > the ARM patch system come to mind).
>> >>
>> >> Note that you don't need to use dim unless you become a committer or a
>> >> maintainer to a tree that's maintained using dim.
>> >
>> > Which unfortunately cannot be said about the ARM patch system...
>>
>> Is there some docs about this ARM patch systems? Or just a link to
>> what it is? I've never heard of it, until this thread here.
>
> http://www.arm.linux.org.uk/developer/patches/info.php

Thanks.

> It does take git-send-email patches, IFF they follow the rules.
>
> I've just discovered it's even linked to from Documentation/arm/README,
> which is horridly out-of-date (2.6? FTP?).

>From a quick look: This is essentially another reimplementation of the
patchwork idea (but probably predating that)? With the difference it's
not all that accepting as patchwork, and it doesn't just automatically
read a mailing list en-passant. Or am I off the mark?
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch