linux-kernel - Re: [PATCH RFC] MAINTAINERS: Add section for subsystem shortname

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CALF0-+WcUzsQ3b3gyCoauAYmmV3xDT7H1veKkabhvC8hofCWAA@mail.gmail.com>
Date:	Tue, 2 Oct 2012 10:08:13 -0300
From:	Ezequiel Garcia <elezegarcia@...il.com>
To:	Peter Senna Tschudin <peter.senna@...il.com>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>, joe@...ches.com,
	gregkh@...uxfoundation.org, davem@...emloft.net, arnd@...db.de,
	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 9:53 AM, Peter Senna Tschudin
<peter.senna@...il.com> wrote:
> On Tue, Oct 2, 2012 at 2:40 PM, Ezequiel Garcia <elezegarcia@...il.com> wrote:
>> On Tue, Oct 2, 2012 at 9:33 AM, Peter Senna Tschudin
>> <peter.senna@...il.com> wrote:
>>> 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.
>>>
>>
>> Perhaps you should do get_maintainer.pl changes yourself and then
>> use it to test on some of your patches to see what subject it produces.
> What are your doubts about this method of getting the short name?
>

No doubts so far since I haven't seen it in action.
Some script results and more examples could help.

>>
>> Then it's easier to see if the proposal makes sense.
>> A new rule / standard is something hard to push and we want to have as much
>> facts as possible to make better decisions.
> The fact is that currently there is no standard way of getting the
> short name for a subsystem. My proposal fixes it allowing to look on
> the MAINTAINERS file to see what short name to use.
>

There is no standard way of getting short name, and there isn't standard
way of naming a patch either.

Just looking through media list I can spot lots of different subject schemes:
  [media] foo: fix some bug
  media: foo: fix some bug
  foo: fix some bug
  Some random text and fix some bug

Regards,
Ezequiel.
--
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/