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 19:05:37 +0100 [thread overview]
Message-ID: <20120902180537.GB31141@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1346606781.7787.25.camel@deadeye.wl.decadent.org.uk>
On Sun, Sep 02, 2012 at 06:26:21PM +0100, Ben Hutchings wrote:
> On Sun, 2012-09-02 at 18:04 +0100, Russell King - ARM Linux wrote:
> > 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.
>
> When someone sends a patch that they want to be applied in mainline and
> then later in stable updates, they must include the cc: line in the
> commit message. Actually cc'ing to the stable list is optional.
>
> When someone sends a preliminary version of a patch for discussion, and
> that might, after proper submission, be wanted in stable updates, that
> line is not necessary. The patch should however have '[RFC]' in the
> subject, so everyone understands that this is not a request for the
> patch to be applied. This should not result in a form response.
You're still saying something different from the DOCUMENTED position
and you're still refusing to accept that you are - even after I've
quoted the _exact_ text which is _very_ _clear_.
Please fix the documentation.
next prev parent reply other threads:[~2012-09-02 18:05 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
2012-09-02 17:26 ` Ben Hutchings
2012-09-02 18:05 ` Russell King - ARM Linux [this message]
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=20120902180537.GB31141@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).