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>] [day] [month] [year] [list]
Date:	Wed, 03 Jul 2013 12:07:40 +0200
From:	Yann Droneaud <ydroneaud@...eya.com>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-kernel@...r.kernel.org, xfs@....sgi.com, ydroneaud@...eya.com
Subject: Re: [PATCH] MAINTAINERS: xfs@....sgi.com is a list

Le 03.07.2013 11:50, Dave Chinner a écrit :
> On Wed, Jul 03, 2013 at 11:36:39AM +0200, Yann Droneaud wrote:
>> Le 03.07.2013 11:24, Dave Chinner a écrit :
>> >On Wed, Jul 03, 2013 at 10:14:41AM +0200, Yann Droneaud wrote:
>> >>Le 03.07.2013 08:40, Dave Chinner a écrit :
>> >>>On Tue, Jul 02, 2013 at 05:00:47PM +0200, Yann Droneaud wrote:
>> >>>>This patch changes type of xfs@....sgi.com
>> >>>>
>> >>>>The output of ./scripts/get_maintainer.pl is
>> >>>>modified to report xfs@....sgi.com as a list:
>> >>>
>> >>>What's the problem with that? All XFS patches and problem
>> >>>reports should be sent to the xfs@....sgi.com list. There are far
>> >>>more people than just the maintainer that can triage problems,
>> >>>answer questions and review patches...
>> >>>
>> >>
>> >>It was just disturbing: I was looking for a list for XFS
>> >>and found only maintainers.
>> >
>> >That's what the:
>> >
>> >L:      xfs@....sgi.com
>> >
>> >entry is, yes?
>> >
>> 
>> In the output of ./scripts/get_maintainer.pl:
>> 
>> Ben Myers <bpm@....com> (supporter:XFS FILESYSTEM)
>> Alex Elder <elder@...nel.org> (supporter:XFS FILESYSTEM)
>> xfs@....sgi.com (supporter:XFS FILESYSTEM)
>> linux-kernel@...r.kernel.org (open list)
> 
> You're smarter than a dumb script. If the information that the
> script parses is correct and the dumb script doesn't give you the
> right information, then what needs fixing?
> 

And what about:

   If you are the only one[*] to abuse ./scripts/get_maintainer.pl,
   then what needs fixing ?

[*] I have found three other examples of duplicating mailing list as 
maintainer:

$ sed -n 's/^L:[[:space:]]*//p' MAINTAINERS | sort | uniq > L
$ sed -n 's/^M:[[:space:]]*//p' MAINTAINERS | sort | uniq > M
$ comm -12 L M
ceph-devel@...r.kernel.org
dm-devel@...hat.com
xfs@....sgi.com

I've sent a patch for xfs@....sgi.com and dm-devel@...hat.com,
in my first pass I've missed ceph-devel@...r.kernel.org

> Seriously, all you are proving is the old adage that
> scripts/get_maintainer.pl should be considered harmful because
> people use it without first engaging their brain.

Just thinking about the whole picture.
In this case ./scripts/get_maintainer.pl is going to be right most of 
time
except for 3 subsystems on about 1160. So having the same address for 
maintainer
and list is a rather uncommon case. Which could be misleading for most.

Regards.

-- 
Yann Droneaud
OPTEYA

--
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