mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	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 16:09:17 +0000	[thread overview]
Message-ID: <20140122160917.GI17314@sirena.org.uk> (raw)
In-Reply-To: <1390395744.31946.45.camel@joe-AO722>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

On Wed, Jan 22, 2014 at 05:02:24AM -0800, Joe Perches wrote:
> On Wed, 2014-01-22 at 13:27 +0100, Ingo Molnar wrote:
> > * Joe Perches <joe@perches.com> wrote:

> > You have cut out my main argument from you reply and have ignored it:

> Not ignored.  Threaded email works fine.

> Your main argument is that some people don't cc lkml
> because section entries don't specify it explicitly.

> My main argument, which you elided, is that some people
> will not cc lkml because they will see some sections
> with L: entries with lkml and others without, and will
> therefore _not_ cc lkml instead.

> So I think the rule should be either every section has
> an lkml entry or no section does.

> Pick one.

> Mixing styles just causes a different type of error.

The other option is that we just don't worry if people CC lkml or not -
for things with a dedicated list it's not super critical that people CC
to lkml and in practice doing so would make it even harder to work with
than it is at the minute.  If they want to do so that's fine and it
shouldn't be a problem but at this point it's questionable if this is
something that we actively want to encourge.

In practice this is exactly what's been happening for years anyway so
it's not something I'd expect to be controversial.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2014-01-22 16:10 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
2014-01-22 13:02     ` Joe Perches
2014-01-22 16:09       ` Mark Brown [this message]
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=20140122160917.GI17314@sirena.org.uk \
    --to=broonie@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=mingo@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

all inboxes | Powered by JetHome®