public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Yann Droneaud <ydroneaud@opteya.com>
Cc: 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 02:54:10 -0700	[thread overview]
Message-ID: <1372845250.2048.7.camel@joe-AO722> (raw)
In-Reply-To: <5e9d66217e0fa968863177d73dd492b1@meuh.org>

On Wed, 2013-07-03 at 11:36 +0200, Yann Droneaud wrote:
> 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)
> 
> [If having the mailing list listed as the maintainer/supporter is 
> correct,
>   could ./scripts/get_maintainer.pl also report the mailing list as a 
> list ?]

It does when you ask for just the lists...

$ ./scripts/get_maintainer.pl -f -l -nom fs/xfs
xfs@oss.sgi.com (open list:XFS FILESYSTEM)
linux-kernel@vger.kernel.org (open list)

If it bothers you that the same email address
doesn't get reported as both a maintainer and
a mailing list, you're free to submit a patch
to get_maintainer.pl. (look at sub add_role)

It doesn't bother me.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-07-03  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-07-03 10:07 Yann Droneaud

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=1372845250.2048.7.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    --cc=ydroneaud@opteya.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