[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <555CF034.5090704@nod.at>
Date: Wed, 20 May 2015 22:36:04 +0200
From: Richard Weinberger <richard@....at>
To: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
CC: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Tim Waugh <tim@...erelk.net>, Jean Delvare <jdelvare@...e.de>,
Wolfram Sang <wsa@...-dreams.de>,
Willy Tarreau <willy@...a-x.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>, linux-i2c@...r.kernel.org,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH 6/6] MAINTAINERS: maintain parport
Am 20.05.2015 um 18:33 schrieb One Thousand Gnomes:
> On Wed, 20 May 2015 17:46:44 +0200
> Richard Weinberger <richard.weinberger@...il.com> wrote:
>
>> On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee
>> <sudipm.mukherjee@...il.com> wrote:
>>> Lets give the parport subsystem a proper name and start
>>> maintaining the files.
>>
>> Excuse me, but usually someone takes over the maintainer role after
>> proving that he
>> cares for a sub system for a certain period of time.
>> Or did I miss something?
>
> It currently (and for some time) has had no maintainer so having a
> maintainer is IMHO definitely an improvement in things.
Having a maintainer is good.
All I wanted to point out was that it is IMHO uncommon to claim maintainership
before being the main contributor or the de facto maintainer of a
subsystem.
This "rule" prevents us from "Mommy!!! Look, I'm a maintainer!!!1" patches. ;-)
Thanks,
//richard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists