From: Greg KH <gregkh@suse.de>
To: Chuck Wolber <chuckw@quantumlinux.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
"Theodore Ts'o" <tytso@mit.edu>,
Randy Dunlap <rdunlap@xenotime.net>,
Dave Jones <davej@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, alan@lxorguk.ukuu.org.uk,
trivial@rustcorp.com.au
Subject: Re: [PATCH] Documentation/stable_kernel_rules.txt: Clarification
Date: Sun, 29 Jan 2006 09:10:47 -0800 [thread overview]
Message-ID: <20060129171047.GA10467@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.63.0601290032110.7252@localhost.localdomain>
On Sun, Jan 29, 2006 at 01:50:16AM -0800, Chuck Wolber wrote:
>
> This reflects the clarification made on what patches the -stable team
> accepts. This applies cleanly to the 2.6.16-rc1 kernel.
>
> Signed-off-by: Chuck Wolber <chuckw@quantumlinux.com>
> ---
>
> --- a/Documentation/stable_kernel_rules.txt 2006-01-16 23:44:47.000000000 -0800
> +++ b/Documentation/stable_kernel_rules.txt 2006-01-29 01:45:44.000000000 -0800
> @@ -18,6 +18,7 @@
> whitespace cleanups, etc).
> - It must be accepted by the relevant subsystem maintainer.
> - It must follow the Documentation/SubmittingPatches rules.
> + - Patches for any 2.6 stable kernel release will be considered.
No, this isn't true.
People complained that we immediatly abandonded the last stable kernel
when a new one came out, so we said we would take patches for a bit on
the last series if people wanted to send them.
That's all, it's not some confusing thing, and we are very much not
going to accept patches for "any" kernel release.
So no, I'm not going to accept this.
thanks,
greg k-h
>
>
> Procedure for submitting patches to the -stable tree:
--
next prev parent reply other threads:[~2006-01-29 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 9:50 [PATCH] Documentation/stable_kernel_rules.txt: Clarification Chuck Wolber
2006-01-29 17:10 ` Greg KH [this message]
2006-01-29 19:52 ` Chuck Wolber
2006-01-29 21:04 ` Greg KH
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=20060129171047.GA10467@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chuckw@quantumlinux.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.org \
--cc=torvalds@osdl.org \
--cc=trivial@rustcorp.com.au \
--cc=tytso@mit.edu \
--cc=zwane@arm.linux.org.uk \
/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