From: Adrian Bunk <bunk@stusta.de>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Pavel Machek <pavel@suse.cz>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
stable@kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.16.y series
Date: Mon, 10 Jul 2006 18:54:29 +0200 [thread overview]
Message-ID: <20060710165429.GB13938@stusta.de> (raw)
In-Reply-To: <44AE558D.9000906@linuxtv.org>
On Fri, Jul 07, 2006 at 08:37:33AM -0400, Michael Krufky wrote:
> Pavel Machek wrote:
>
> >Is it still okay to submit patches for 2.6.16-stable? I guess "dirty
> >buffers flushing broken after resume" may count...
> > Pavel
> >
> >
> I was under the impression that 2.6.16.y was staying open for a much
> longer time, as per Adrian's "2.6.16 long living kernel" announcement a
> short while back.
>
> I just assumed that the Greg and Chris were handling it until 2.6.18
> gets released, and then Adrian takes over 2.6.16.y while the [stable]
> team moves on to 2.6.17.y and 2.6.18.y ... Was this an incorrect
> assumption?
Greg told me they want to make one last 2.6.16.y release.
Greg and Chris don't maintain two series that long - check the date of
the last 2.6.15.y release.
> ...and if not, should 2.6.16.y patches always be sent to
> stable@kernel.org, or will Adrian have an alternate method for accepting
> patches?
This is among the small technical issues that have to be discussed and
solved.
> -Mike
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-07-10 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 22:25 Linux 2.6.16.24 Greg KH
2006-07-06 22:28 ` Greg KH
2006-07-07 10:54 ` Pavel Machek
2006-07-07 12:37 ` Linux 2.6.16.y series Michael Krufky
2006-07-10 16:54 ` Adrian Bunk [this message]
2006-07-10 16:43 ` David Lang
2006-07-11 22:36 ` 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=20060710165429.GB13938@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=pavel@suse.cz \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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