From: Joe Perches <joe@perches.com>
To: Ingo Molnar <mingo@kernel.org>
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 05:02:24 -0800 [thread overview]
Message-ID: <1390395744.31946.45.camel@joe-AO722> (raw)
In-Reply-To: <20140122122728.GA8882@gmail.com>
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.
> Which is not a very honest way to conduct discussions :-(
[]
> > 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.
If you are going to complain about "honesty in
argumentation", try it yourself.
Be an exemplar.
Describing a previous change as being made for
intuitions sake when it wasn't, isn't.
cheers, Joe
next prev parent reply other threads:[~2014-01-22 13:02 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 [this message]
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=1390395744.31946.45.camel@joe-AO722 \
--to=joe@perches.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=hpa@zytor.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®