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: Tue, 12 Apr 2016 00:31:51 +0100 [thread overview]
Message-ID: <570C33E7.2060906@youngman.org.uk> (raw)
In-Reply-To: <1460415825.1800.100.camel@perches.com>
On 12/04/16 00:03, Joe Perches wrote:
> 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.
Ahh ... you are ASS U ME ing that it is a personal email address. Why?
And that person is going to get overwhelmed if the system is busy ...
I can't speak for anyone else, but if I were a maintainer I would more
consider myself an integrator. If patches are NOT sent to the list, then
there are two *likely* scenarios. Either
Good patches get dropped because there is no discussion, or
Bad patches get forwarded because there is no discussion.
(And on linux-raid, where I'm reading this, I think this is very much
the current state of affairs. Neil Brown has stepped down, and iirc the
person who has taken over actively wants the list to review things.)
You are assuming that "FullName" refers to a person. If I were a
maintainer I would personally be very upset with that state of affairs.
Why shouldn't "FullName" be the full name of a mailing list?
If I were a maintainer, it would be "not vetted by the mailing list? Not
going nowhere, nohow". Patches get sent to the mailing list, or they get
ignored.
Cheers,
Wol
next prev parent reply other threads:[~2016-04-11 23:31 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
2016-04-11 23:31 ` Wols Lists [this message]
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=570C33E7.2060906@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 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.