From: Andrew Morton <akpm@zip.com.au>
To: Heinz Diehl <hd@cavy.de>
Cc: linux-kernel@vger.kernel.org, sct@redhat.com
Subject: Re: [2.5.26] ext3 from Dec. 2001?
Date: Sun, 21 Jul 2002 21:53:18 -0700 [thread overview]
Message-ID: <3D3B8FBE.D5C11685@zip.com.au> (raw)
In-Reply-To: 20020720151600.GA268@chiara.cavy.de
Heinz Diehl wrote:
>
> Hi!
>
> Just a short question: is there a patch for 2.5.26 to update ext3 to
> ext3-0.9.18? There's still ext3-0.9.16 from Dec. 2001 present in 2.5.26.
> At ../people/sct on ftp.kernel.org there are only updates for kernel
> 2.2 and 2.4.
2.5 is uptodate wrt the current ext3-for-2.4 development tree.
That means that it's more uptodate than 2.4 is...
Some recent changes to ext3 have exposed a data=journal bug
in 2.5 which is also present in 2.4, but is much harder to hit
there. I'm not sure what Stephen's intentions are on a 2.4
upgrade, but I'd be inclined to sit tight until 2.4.20-pre.
-
next prev parent reply other threads:[~2002-07-22 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 15:16 [2.5.26] ext3 from Dec. 2001? Heinz Diehl
2002-07-22 4:53 ` Andrew Morton [this message]
2002-07-22 17:31 ` Stephen C. Tweedie
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=3D3B8FBE.D5C11685@zip.com.au \
--to=akpm@zip.com.au \
--cc=hd@cavy.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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