public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Reuben Farrelly <reuben-lkml@reub.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.15-rc1-mm1
Date: Fri, 18 Nov 2005 08:56:58 +0100	[thread overview]
Message-ID: <20051118075656.GA8311@favonius> (raw)
In-Reply-To: <20051117234252.087fa813.akpm@osdl.org>

Andrew Morton wrote (ao):
> Reuben Farrelly <reuben-lkml@reub.net> wrote:
> > On 18/11/2005 8:18 a.m., Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc1/2.6.15-rc1-mm1
> > > 
> > > - reiser4 significantly updated
> > > 
> > > 
> > > 
> > > 
> > > Changes since 2.6.14-mm2:
> > 
> > This has been one of the best -mm releases in a while.  No problems compiling
> > or running - and so far nearly 18 hours uptime without any surprises.

I second this. It is stable under (my) load where the 2.6.14-mm releases
crashed. Most likely due to Reiser4, but couldn't capture anything yet
(netconsole troubles, have to investigate more) so not sure.

Reiser4 is very slow though, as is discussed on the reiserfs list atm.

> We'll have to try harder.  -mm2 is up there now, to break everything again.

Nice :-)

-- 
Humilis IT Services and Solutions
http://www.humilis.net

  reply	other threads:[~2005-11-18  7:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17 19:18 2.6.15-rc1-mm1 Andrew Morton
2005-11-17 21:30 ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-17 22:14   ` 2.6.15-rc1-mm1 David Howells
2005-11-17 22:23     ` 2.6.15-rc1-mm1 Valdis.Kletnieks
2005-11-18  4:23       ` 2.6.15-rc1-mm1 - immediate system reset at boot Valdis.Kletnieks
2005-11-18  4:27         ` Andrew Morton
2005-11-18  1:41 ` [-mm patch] kernel/signal.c: fix compile warning Adrian Bunk
2005-11-18  3:59   ` George Anzinger
2005-11-18  1:44 ` 2.6.15-rc1-mm1 Richard Knutsson
2005-11-18  1:53   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:20 ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18  7:42   ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18  7:56     ` Sander [this message]
2005-11-18 20:58     ` 2.6.15-rc1-mm1 Reuben Farrelly
2005-11-18 21:19       ` 2.6.15-rc1-mm1 Andrew Morton
2005-11-18 12:43 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 20:37   ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 21:14     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-18 23:16       ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:03         ` 2.6.15-rc1-mm1 Greg KH
2005-11-18 23:35         ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-18 23:51           ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:24             ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-19  1:26               ` 2.6.15-rc1-mm1 Greg KH
2005-11-19  1:49                 ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  3:24                 ` 2.6.15-rc1-mm1 Ed Tomlinson
2005-11-21  0:00                   ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-21  0:26                   ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 20:47                     ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-22 20:55                       ` 2.6.15-rc1-mm1 Greg KH
2005-11-22 22:05                         ` 2.6.15-rc1-mm1 Ian McDonald
2005-11-19  1:40               ` 2.6.15-rc1-mm1 Ian McDonald

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=20051118075656.GA8311@favonius \
    --to=sander@humilis.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reuben-lkml@reub.net \
    /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