From: Wols Lists <antlists@youngman.org.uk>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>, Shaohua Li <shli@kernel.org>,
dm-devel@redhat.com, linux-raid@vger.kernel.org,
Joe Perches <joe@perches.com>
Subject: Re: [PATCH] MAINTAINERS: correct entry for LVM
Date: Mon, 11 Apr 2016 19:50:03 +0100 [thread overview]
Message-ID: <570BF1DB.1040700@youngman.org.uk> (raw)
In-Reply-To: <570BD354.2000100@gmail.com>
On 11/04/16 17:39, Sudip Mukherjee wrote:
> On Monday 11 April 2016 09:53 PM, Alasdair G Kergon wrote:
>> On Mon, Apr 11, 2016 at 09:45:01PM +0530, Sudip Mukherjee wrote:
>>> L stands for "Mailing list that is relevant to this area", and this is a
>>> mailing list. :)
>>
>> Your proposed patch isn't changing the L entry, so this is of no
>> relevance.
>
> Sorry, I am not understanding.
>
> The current entry in MAINTAINERS is:
> DEVICE-MAPPER (LVM)
> M: Alasdair Kergon <agk@redhat.com>
> M: Mike Snitzer <snitzer@redhat.com>
> M: dm-devel@redhat.com
> L: dm-devel@redhat.com
> ...
>
> So my patch just removed the line : "M: dm-devel@redhat.com"
>
> So now the entry becomes :
> DEVICE-MAPPER (LVM)
> M: Alasdair Kergon <agk@redhat.com>
> M: Mike Snitzer <snitzer@redhat.com>
> L: dm-devel@redhat.com
> ...
>
> So, now it correctly shows dm-devel@redhat.com as a mailing list which
> should have cc to all the patches related to LVM.
>
> Or am I understanding this wrong?
Yes. Because (I guess M stands for maintainer) this list has maintainer
status. As all patches should be sent to the maintainers therefore all
patches should be sent to this list.
The same person can appear twice in a phone book, once under their name
and once under their job title. This is exactly the same situation -
this list should appear once as a list to tell people that it's a list,
AND ALSO as a maintainer to tell people that patches must be sent to the
list.
I guess English is not your first language, but the important point is
that M and L are not mutually exclusive.
Cheers,
Wol
next prev parent reply other threads:[~2016-04-11 18:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 15:20 [PATCH] MAINTAINERS: correct entry for LVM Sudip Mukherjee
2016-04-11 15:51 ` Alasdair G Kergon
2016-04-11 16:15 ` Sudip Mukherjee
2016-04-11 16:23 ` Alasdair G Kergon
2016-04-11 16:39 ` Sudip Mukherjee
2016-04-11 18:50 ` Wols Lists [this message]
2016-04-11 21:08 ` Joe Perches
2016-04-11 22:25 ` Wols Lists
2016-04-11 23:03 ` Joe Perches
2016-04-11 23:31 ` Wols Lists
2016-04-11 23:43 ` Joe Perches
2016-04-12 5:31 ` Sudip Mukherjee
2016-04-11 23:52 ` Mike Snitzer
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=570BF1DB.1040700@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=agk@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dm-devel@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
--cc=sudipm.mukherjee@gmail.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;
as well as URLs for NNTP newsgroup(s).