linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Joshua Hudson <joshudson@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Stability of 2.6.17-rc3?
Date: Wed, 10 May 2006 10:41:14 +0100	[thread overview]
Message-ID: <200605101041.14595.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0605100931250.27657@yvahk01.tjqt.qr>

On Wednesday 10 May 2006 08:34, Jan Engelhardt wrote:
> > 2.6.17-rc3 is a development kernel, no guarantees about anything really.
> > Development kernels are run completely at your own risk. It may run
> > fine, it may explode at boot, [...], it may eat your lunch, it may cause
> > an alien invasion -[...]
>
> Quite a list. So what can -mm kernels make go wrong more? :-]

Well, back in the 2.5 days, JFS/-mm ate my filesystem, which is possibly worse 
than it eating my lunch, and more relevant to me than an alien invasion...

Though, Joshua, 2.6.17-rc3 seems to be a rock-solid release. It's safe enough 
to diff against and boot, if that's what you want to do.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-05-10  9:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 20:40 Stability of 2.6.17-rc3? Joshua Hudson
2006-05-09 22:01 ` Jesper Juhl
2006-05-10  7:34   ` Jan Engelhardt
2006-05-10  9:41     ` Alistair John Strachan [this message]
2006-05-10 22:23       ` Jan Engelhardt
2006-05-11  0:19         ` Alistair John Strachan
2006-05-11 11:23           ` Jan Engelhardt
2006-05-10  7:31 ` Jan Engelhardt

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=200605101041.14595.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=joshudson@gmail.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).