linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joshua Hudson" <joshudson@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Stability of 2.6.17-rc3?
Date: Tue, 9 May 2006 13:40:37 -0700	[thread overview]
Message-ID: <bda6d13a0605091340x2e16342v15733b2c9612d985@mail.gmail.com> (raw)

Was hoping 2.6.17 would be out within one week, doesn't look like it
is going to happen.
My thesis defense is coming up, need to merge my patches against some kernel
(requiring 2.6.16.1 looks weird).

On a machine that 2.6.16.1 runs bug-free, is it sane to assume
2.6.17-rc3 will as well?
If it fails outright, I can revert, but if it is unstable I'm going to
have some problems.
(You would be surprised how long it took me to discover a mistake that
sys_rename(on any filesystem) -> deadlock with my custom patch).

             reply	other threads:[~2006-05-09 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 20:40 Joshua Hudson [this message]
2006-05-09 22:01 ` Stability of 2.6.17-rc3? Jesper Juhl
2006-05-10  7:34   ` Jan Engelhardt
2006-05-10  9:41     ` Alistair John Strachan
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=bda6d13a0605091340x2e16342v15733b2c9612d985@mail.gmail.com \
    --to=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).