linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Maybe 2.6.10.1 ?
@ 2005-01-08 10:25 Maciej Soltysiak
  2005-01-09  1:35 ` Jesper Juhl
  0 siblings, 1 reply; 2+ messages in thread
From: Maciej Soltysiak @ 2005-01-08 10:25 UTC (permalink / raw)
  To: linux-kernel

Hello,

Maybe we should release 2.6.10.1 with those security fixes,
so people maintaining other trees like: -tiny, -ck, -grsec,
release patches over the fixed ones. Users won't miss the
fixes if they prefer some trees instead of vanilla.

What do you think?

Regars,
Maciej



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Maybe 2.6.10.1 ?
  2005-01-08 10:25 Maybe 2.6.10.1 ? Maciej Soltysiak
@ 2005-01-09  1:35 ` Jesper Juhl
  0 siblings, 0 replies; 2+ messages in thread
From: Jesper Juhl @ 2005-01-09  1:35 UTC (permalink / raw)
  To: Maciej Soltysiak; +Cc: linux-kernel

On Sat, 8 Jan 2005, Maciej Soltysiak wrote:

> Hello,
> 
> Maybe we should release 2.6.10.1 with those security fixes,
> so people maintaining other trees like: -tiny, -ck, -grsec,
> release patches over the fixed ones. Users won't miss the
> fixes if they prefer some trees instead of vanilla.
> 
> What do you think?
> 
I'd suggest (and I'm a comlete nobody in this regard) that instead Linus 
takes the security fixes + whatever he and Andrew deems to be "obviously 
correct and with zero risk of causing trouble" from the current -bk and 
turns that into 2.6.11-rc1, then let that stew for 2 or 3 days, then 
unless someone sees something horribly wrong, release it as 2.6.11 - then 
take whatever else is in current -bk and adds it and then that'll be 
2.6.11-bk1 and we move on from there.

-- 
Jesper Juhl




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-01-09  1:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-08 10:25 Maybe 2.6.10.1 ? Maciej Soltysiak
2005-01-09  1:35 ` Jesper Juhl

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).