From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754556AbbETUgQ (ORCPT <rfc822;w@1wt.eu>);
	Wed, 20 May 2015 16:36:16 -0400
Received: from a.ns.miles-group.at ([95.130.255.143]:65276 "EHLO radon.swed.at"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754505AbbETUgL (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 20 May 2015 16:36:11 -0400
Message-ID: <555CF034.5090704@nod.at>
Date: Wed, 20 May 2015 22:36:04 +0200
From: Richard Weinberger <richard@nod.at>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
CC: Sudip Mukherjee <sudipm.mukherjee@gmail.com>, Tim Waugh <tim@cyberelk.net>,
        Jean Delvare <jdelvare@suse.de>, Wolfram Sang <wsa@the-dreams.de>,
        Willy Tarreau <willy@meta-x.org>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        LKML <linux-kernel@vger.kernel.org>, linux-i2c@vger.kernel.org,
        "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH 6/6] MAINTAINERS: maintain parport
References: <1432135622-8288-1-git-send-email-sudipm.mukherjee@gmail.com>	<1432135622-8288-7-git-send-email-sudipm.mukherjee@gmail.com>	<CAFLxGvyw+UhHrdbiXCkKefirjiOum2+cNY26zDe2AzAi0hx0ng@mail.gmail.com> <20150520173324.3090a6d7@lxorguk.ukuu.org.uk>
In-Reply-To: <20150520173324.3090a6d7@lxorguk.ukuu.org.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Am 20.05.2015 um 18:33 schrieb One Thousand Gnomes:
> On Wed, 20 May 2015 17:46:44 +0200
> Richard Weinberger <richard.weinberger@gmail.com> wrote:
> 
>> On Wed, May 20, 2015 at 5:27 PM, Sudip Mukherjee
>> <sudipm.mukherjee@gmail.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