From: Yann Droneaud <ydroneaud@opteya.com>
To: Dave Chinner <david@fromorbit.com>
Cc: ydroneaud@opteya.com, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] MAINTAINERS: xfs@oss.sgi.com is a list
Date: Wed, 03 Jul 2013 12:07:40 +0200 [thread overview]
Message-ID: <ea519baa117add8c12bbe65f77708a4d@meuh.org> (raw)
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@oss.sgi.com
>> >>>>
>> >>>>The output of ./scripts/get_maintainer.pl is
>> >>>>modified to report xfs@oss.sgi.com as a list:
>> >>>
>> >>>What's the problem with that? All XFS patches and problem
>> >>>reports should be sent to the xfs@oss.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@oss.sgi.com
>> >
>> >entry is, yes?
>> >
>>
>> In the output of ./scripts/get_maintainer.pl:
>>
>> Ben Myers <bpm@sgi.com> (supporter:XFS FILESYSTEM)
>> Alex Elder <elder@kernel.org> (supporter:XFS FILESYSTEM)
>> xfs@oss.sgi.com (supporter:XFS FILESYSTEM)
>> linux-kernel@vger.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@vger.kernel.org
dm-devel@redhat.com
xfs@oss.sgi.com
I've sent a patch for xfs@oss.sgi.com and dm-devel@redhat.com,
in my first pass I've missed ceph-devel@vger.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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-07-03 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 10:07 Yann Droneaud [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-02 15:00 [PATCH] MAINTAINERS: xfs@oss.sgi.com is a list Yann Droneaud
2013-07-03 6:40 ` Dave Chinner
2013-07-03 8:14 ` Yann Droneaud
2013-07-03 9:24 ` Dave Chinner
2013-07-03 9:36 ` Yann Droneaud
2013-07-03 9:50 ` Dave Chinner
2013-07-03 9:54 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ea519baa117add8c12bbe65f77708a4d@meuh.org \
--to=ydroneaud@opteya.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox