From: "Markus Hästbacka" <midian@ihme.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1-rc1 affected?
Date: Mon, 05 Jan 2004 21:04:47 +0200 [thread overview]
Message-ID: <1073329487.21682.17.camel@midux> (raw)
In-Reply-To: <Pine.LNX.4.58.0401051027430.2115@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Mon, 2004-01-05 at 20:31, Linus Torvalds wrote:
> Because nobody actually contacted me about the problem and I read about it
> on linux-kernel like everybody else? Because I just got up and created the
> patch? And because nobody has an exploit yet, and one may be hard or
> impossible to create? And because people who care about these things tend
> to not update to x.0 kernels anyway?
>
Ok, I see your point. though, even that I care about these things, I
updated one of my servers to development tree somewhere at 2.5.70~.
The reason for me was the major performance difference.
> > But I think there's corporations who use 2.6.0 and don't read the lkml.
>
> They'll get a 2.6.1 soonish. The patch is in the current BK tree, will be
> in -rc2, and will be in 2.6.1. Let's just make sure we don't screw up the
> release due to being too much in a hurry either..
>
Yes, better give it time and not rush.
Thanks for your time.
--
"Software is like sex, it's better when it's free."
Markus Hästbacka <midian at ihme dot org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-05 19:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 16:31 2.6.1-rc1 affected? Markus Hästbacka
2004-01-05 16:41 ` [patchlet link] " Maciej Soltysiak
2004-01-05 16:46 ` Linus Torvalds
2004-01-05 18:14 ` Markus Hästbacka
2004-01-05 18:31 ` Linus Torvalds
2004-01-05 19:04 ` Markus Hästbacka [this message]
2004-01-05 19:38 ` GCS
2004-01-05 22:48 ` Tomas Szepe
2004-01-06 0:23 ` Bastiaan Spandaw
2004-01-06 1:09 ` Max Valdez
2004-01-06 1:25 ` Jesper Juhl
2004-01-06 1:31 ` Hugang
2004-01-06 1:43 ` Hugang
2004-01-06 2:47 ` szonyi calin
2004-01-06 3:24 ` Jonathan Higdon
2004-01-06 3:51 ` szonyi calin
2004-01-06 6:39 ` Jakob Oestergaard
2004-01-06 9:26 ` Giuliani Ivan
[not found] <1aFW7-39l-11@gated-at.bofh.it>
[not found] ` <1aG5G-3mf-21@gated-at.bofh.it>
2004-01-06 12:44 ` Michal Schmidt
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=1073329487.21682.17.camel@midux \
--to=midian@ihme.org \
--cc=linux-kernel@vger.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