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: <46C0C282.800@student.ltu.se>
Date:	Mon, 13 Aug 2007 22:43:46 +0200
From:	Richard Knutsson <ricknu-0@...dent.ltu.se>
To:	"Kok, Auke" <auke-jan.h.kok@...el.com>
CC:	Joe Perches <joe@...ches.com>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch -	scripts/get_maintainer.pl

Kok, Auke wrote:
> Richard Knutsson wrote:
>> Kok, Auke wrote:
>>> Joe Perches wrote:
>>>> I grew weary of looking up the appropriate
>>>> maintainer email address(es) to CC: for a patch.
>>>>
>>>> I added flags to the MAINTAINERS file
>>>>
>>>> F:    file pattern
>>>>
>>>> for each maintained block and a script to parse
>>>> the modified blocks for maintainer and list
>>>> email addresses.
>>>>
>>>> perl scripts/get_maintainer.pl <patch>
>>>>
>>>> gives the appropriate maintainer(s).
>>>>
>>>> Modifications since last post:
>>>>
>>>> Added options to control email address style and multiple address 
>>>> separator
>>>>
>>>> Please apply.
>>> Well, I came up with this implementation, so I definately support it 
>>> and the way Joe implemented it:
>>>
>> Really? Please check out this thread with at least two ideas of 
>> possible implementations, with Stefan Richter as the spokesman of the 
>> current implementation: 
>> http://marc.info/?l=linux-kernel&m=116870578531280&w=3
>> ...and I am not saying there hasn't been someone suggesting it even 
>> earlier.
>>
>> The expression; nothing is new under the sun comes to mind ;)
>>
>> Anyway, glad to see someone actually implementing it. Thanks!
>
> bad wording my side, I never implemented anything, but I did post the 
> "F:" flag idea specific to allocating files to developers on lkml: 
> http://lkml.org/lkml/2007/6/29/300
>
...and so did Stefan: 
http://marc.info/?l=linux-kernel&m=116871954100026&w=3 :)

cu
Richard Knutsson

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ