All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Wols Lists <antlists@youngman.org.uk>,
	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 16:03:45 -0700	[thread overview]
Message-ID: <1460415825.1800.100.camel@perches.com> (raw)
In-Reply-To: <570C2468.7050608@youngman.org.uk>

On Mon, 2016-04-11 at 23:25 +0100, Wols Lists wrote:
> 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".

I think that's not a particularly good definition.
MAINTAINERS describes the M: entry as:

	M: Mail patches to: FullName <address@domain>

That _person_ is generally responsible for vetting patches
and bug fixing.

> By that definition the list is a maintainer.

Not given there's a specific L: entry that's described

	L: Mailing list that is relevant to this area

> And what do you do if you
> don't have a person designated as maintainer?

Then you don't have a maintainer

>  Do you send everything to /dev/null?

Patches are sent to lkml.

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

disagree.

cheers, Joe

  reply	other threads:[~2016-04-11 23:03 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
2016-04-11 21:08           ` Joe Perches
2016-04-11 22:25             ` Wols Lists
2016-04-11 23:03               ` Joe Perches [this message]
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=1460415825.1800.100.camel@perches.com \
    --to=joe@perches.com \
    --cc=agk@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=antlists@youngman.org.uk \
    --cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.