From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: Build dtb files in all target
Date: Sun, 2 Sep 2012 18:04:34 +0100 [thread overview]
Message-ID: <20120902170434.GA31141@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1346594067.4958.7.camel@deadeye.wl.decadent.org.uk>
On Sun, Sep 02, 2012 at 02:54:27PM +0100, Ben Hutchings wrote:
> On Sat, 2012-09-01 at 21:11 +0100, Russell King - ARM Linux wrote:
> [...]
> > It is as clear as mud now when stable at vger.kernel.org should be Cc'd and
> > when it should not.
> [...]
>
> Perhaps what you're missing is that it's an open mailing list (as was
> stable at kernel.org), not an alias for 'the stable team'. As with any
> other kernel mailing list, you don't need to get explicit permission to
> send mail to it. So there is no 'should not'.
Then please explain why people keep getting Greg's standard form "this
is not how you submit patches for stable" when they CC a _discussion_
to the address.
What you're saying does not tie up with what _actually_ happens in
reality. Therefore I can only believe that you are wrong, even though
you may be part of "the stable team".
Please get your (collective) policy sorted out and properly documented,
and you _all_ start behaving consistently. If you want
stable at vger.kernel.org to be a list for discussion of stable patches,
then fine - just don't then send standard form emails telling people
they did something wrong when they _do_ try to use it for discussion.
As I have pointed out many times in this thread, there is inconsistency
between what you are saying, what Greg has said, what the documentation
says, and the reaction that people get from Greg when they do send to
that address. Something needs to change, and that isn't me - it's how
the stable stuff operates. Because it's very confusing and inconsistent
at the moment.
Fix that problem and we can then all move along. Continue to ignore it
and I'll continue my crusade against this blatent inconsistency. :)
next prev parent reply other threads:[~2012-09-02 17:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 5:14 [PATCH v2] ARM: Build dtb files in all target Andrew Lunn
2012-08-30 16:52 ` Jason Cooper
2012-08-30 17:23 ` Russell King - ARM Linux
2012-08-30 18:37 ` Jason Cooper
2012-08-30 19:14 ` Russell King - ARM Linux
2012-08-30 19:40 ` Jason Cooper
2012-08-31 21:11 ` Ben Hutchings
2012-08-31 22:32 ` Russell King - ARM Linux
2012-09-01 14:20 ` Ben Hutchings
2012-09-01 15:25 ` Russell King - ARM Linux
2012-09-01 16:32 ` Jonathan Nieder
2012-09-01 18:22 ` Russell King - ARM Linux
2012-09-01 18:38 ` Jonathan Nieder
2012-09-01 20:11 ` Russell King - ARM Linux
2012-09-02 6:30 ` When to cc stable@vger.kernel.org (Re: [PATCH v2] ARM: Build dtb files in all target) Jonathan Nieder
2012-09-02 13:54 ` [PATCH v2] ARM: Build dtb files in all target Ben Hutchings
2012-09-02 17:04 ` Russell King - ARM Linux [this message]
2012-09-02 17:26 ` Ben Hutchings
2012-09-02 18:05 ` Russell King - ARM Linux
2012-09-02 19:14 ` Uwe Kleine-König
2012-09-02 23:58 ` Greg KH
2012-08-30 18:03 ` Greg KH
2012-09-01 14:49 ` Andrew Lunn
2012-09-03 12:21 ` Dave Martin
2012-09-03 19:55 ` Jason Cooper
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=20120902170434.GA31141@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).