Thread (25 messages) flat view 25 messages, 8 authors, 2012-09-03
STALE5087d

[PATCH v2] ARM: Build dtb files in all target

From: Russell King - ARM Linux <hidden>
Date: 2012-09-02 18:05:37

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:
quoted
On Sun, Sep 02, 2012 at 02:54:27PM +0100, Ben Hutchings wrote:
quoted
On Sat, 2012-09-01 at 21:11 +0100, Russell King - ARM Linux wrote:
[...]
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help