From: Wols Lists <antlists@youngman.org.uk>
To: Joe Perches <joe@perches.com>,
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
Subject: Re: [PATCH] MAINTAINERS: correct entry for LVM
Date: Mon, 11 Apr 2016 23:25:44 +0100 [thread overview]
Message-ID: <570C2468.7050608@youngman.org.uk> (raw)
In-Reply-To: <1460408934.1800.87.camel@perches.com>
On 11/04/16 22:08, Joe Perches wrote:
> I'm a native English speaker and I think that's a not
> a good argument.
>
> Having the same entry for M: and L: where M: isn't an
> actual person is not a great idea.
>
> The list is not a maintainer.
>
>
Depends on your definition of maintainer ...
To me, it means "should be notified of anything maintenance-related". By
that definition the list is a maintainer. And what do you do if you
don't have a person designated as maintainer? Do you send everything to
/dev/null?
A list is for general discussion, advice, whatever. Those two
definitions are not mutually exclusive, and therefore the list email
address may need to be identified as both/and, hence the two entries.
Cheers,
Wol
next prev parent reply other threads:[~2016-04-11 22:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 15:20 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
2016-04-11 21:08 ` Joe Perches
2016-04-11 22:25 ` Wols Lists [this message]
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=570C2468.7050608@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
Powered by JetHome