[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+MoWDqxXPiuFwmznynn8SPK20eJUgCKonq+C=s8fKvcnkb4Aw@mail.gmail.com>
Date: Tue, 2 Oct 2012 14:33:31 +0200
From: Peter Senna Tschudin <peter.senna@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: joe@...ches.com, gregkh@...uxfoundation.org, davem@...emloft.net,
arnd@...db.de, elezegarcia@...il.com, Julia.Lawall@...6.fr,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname
On Tue, Oct 2, 2012 at 2:14 PM, Dan Carpenter <dan.carpenter@...cle.com> wrote:
> On Tue, Oct 02, 2012 at 01:57:04PM +0200, Peter Senna Tschudin wrote:
>> The shortname for a subsystem, that is primarly used when sending patches over E-mail, is not stored anywhere in the source code. Actually one need to dig git log or mailing list archives. There is no standard, and the Maintainer choose how to short name his/her subsystem. MAINTAINERS file is the right place for storing this information.
>>
>> U is the second letter of Subsystem.
>>
>> This will also enable automatic tools like scripts/get_maintainer.pl to provide the correct short name for each filename in the Kernel source tree.
>>
>
> This is pretty useless without a script to parse it. Also none of
With or without a script, there is no default way of finding the short
name. Changing scripts/get_maintainer.pl to do it does not seems very
complex.
> subsystem names you chose as examples are correct. Please line wrap
See? It's not easy to find three examples to put on the text. Can you
please provide three examples?
> your commit message at 72 characters.
Yes. I'll fix it.
Thank you,
Peter
>
> regards,
> dan carpenter
>
--
Peter
--
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