From: Greg KH <gregkh@suse.de>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Doc/stable rules: add new cherry-pick logic
Date: Fri, 4 Dec 2009 08:41:26 -0800 [thread overview]
Message-ID: <20091204164126.GB1981@suse.de> (raw)
In-Reply-To: <20091204111635.GA28059@Chamillionaire.breakpoint.cc>
On Fri, Dec 04, 2009 at 12:16:35PM +0100, Sebastian Andrzej Siewior wrote:
> - it is possible to submit patches for the stable queue without sending
> them directly stable@kernel.org. If the tag (Cc: stable@kernel.org) is
> available in the sign-off area then hpa's script will filter them into
> the stable mailbox once it hits Linus' tree.
> - Patches which require others to be applied first can be also specified.
> This was discussued in http://lkml.org/lkml/2009/11/9/474
>
> Signed-off-by: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
> ---
> Greg, the cherry pick format got acked by stable team didn't it?
>
> Documentation/stable_kernel_rules.txt | 22 +++++++++++++++++++++-
> 1 files changed, 21 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
> index a452227..8c0aaad 100644
> --- a/Documentation/stable_kernel_rules.txt
> +++ b/Documentation/stable_kernel_rules.txt
> @@ -25,7 +25,27 @@ Rules on what kind of patches are accepted, and which ones are not, into the
> Procedure for submitting patches to the -stable tree:
>
> - Send the patch, after verifying that it follows the above rules, to
> - stable@kernel.org.
> + stable@kernel.org. An alternative is to have the tag
> + Cc: stable@kernel.org
> + in the sign-off area. Once the patch is merged it will be filtered
> + into the stable tree even without sending directly to
> + stable@kernel.org
This is already documented (somewhat poorly) in the paragraph a few
bullets below this one that says:
- If the stable@kernel.org address is added to a patch, when it
goes into Linus's tree it will automatically be emailed to
the stable team.
Can you delete this paragraph, as your documentation is much nicer and
makes more sense?
Care to redo this patch that way?
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-04 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 6:48 [PATCH] UBI: flush wl before clearing update marker Artem Bityutskiy
2009-12-02 15:42 ` Greg KH
2009-12-03 7:01 ` Artem Bityutskiy
2009-12-04 1:58 ` Greg KH
2009-12-04 5:42 ` Artem Bityutskiy
2009-12-04 11:16 ` [PATCH] Doc/stable rules: add new cherry-pick logic Sebastian Andrzej Siewior
2009-12-04 16:41 ` Greg KH [this message]
2009-12-06 11:24 ` [PATCH v2] " Sebastian Andrzej Siewior
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=20091204164126.GB1981@suse.de \
--to=gregkh@suse.de \
--cc=Artem.Bityutskiy@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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