From: Ingo Molnar <mingo@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: hpa@zytor.com, alan@linux.intel.com, acme@redhat.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
peterz@infradead.org, paulmck@linux.vnet.ibm.com,
akpm@linux-foundation.org, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/urgent] MAINTAINERS: Restore "L: linux-kernel@vger.kernel.org" entries
Date: Wed, 22 Jan 2014 13:27:28 +0100 [thread overview]
Message-ID: <20140122122728.GA8882@gmail.com> (raw)
In-Reply-To: <1390325069.2472.78.camel@joe-AO722>
* Joe Perches <joe@perches.com> wrote:
> Also, SubmittingPatches had and still has:
>
> 6) Select your CC (e-mail carbon copy) list.
>
> Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
>
> Arguably, that same info should be added to the
> MAINTAINERS header instead of each section.
You have cut out my main argument from you reply and have ignored it:
>> In hindsight removing all the "L: lkml" entries was probably not
>> an overly good idea, not all mechanic duplication should be
>> eliminated: in files read by humans it's useful to have 'at a
>> glance' summary for all email addresses important to a subsystem's
>> maintenance, in a single place, without too many imported rules
>> and assumptions.
Which is not a very honest way to conduct discussions :-(
That section replies to most of your arguments.
> > b5472cddbe2c MAINTAINERS: remove L: linux-kernel@vger.kernel.org from all but "THE REST"
> >
> > So it turns out that it's all but intuitive, not all people
> > use scripts/get_maintainer.pl to extract maintainer contact info,
> > some people read the MAINTAINERS file and see the lack of 'L:' entries
> > of various lkml-only subsystems and are sending patches to the
> > maintainers only, without Cc:-ing lkml. They arguably have a point.
>
> shrug, I think it would be better if people
> used get_maintainer more often.
People are people, they'll use well constructed human-readable sources
of information like the MAINTAINERS file just fine.
> MAINTAINERS already says:
That's irrelevant really, reality tells us that good people are
looking at the entries and are using them as-is. For such things
technology should adapt to people, not the other way around.
> > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > @@ -4655,6 +4657,7 @@ F: net/irda/
> > IRQ SUBSYSTEM
> > M: Thomas Gleixner <tglx@linutronix.de>
> > S: Maintained
> > +L: linux-kernel@vger.kernel.org
>
> If this is done, can you please standardize on
> placing the L: line immediately after the M: line
> and before the S: line as was done for all the
> other added lines.
Good point, fixed.
Thanks,
Ingo
next prev parent reply other threads:[~2014-01-22 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 15:49 tip-bot for Ingo Molnar
2014-01-21 17:24 ` Joe Perches
2014-01-22 12:27 ` Ingo Molnar [this message]
2014-01-22 13:02 ` Joe Perches
2014-01-22 16:09 ` Mark Brown
2014-01-22 17:30 ` Joe Perches
2014-01-22 18:06 ` Mark Brown
2014-01-22 18:18 ` Joe Perches
2014-01-22 17:36 ` Ingo Molnar
2014-01-22 17:47 ` Joe Perches
2014-01-22 12:27 tip-bot for Ingo Molnar
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=20140122122728.GA8882@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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