From: Chris Mason <mason@suse.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix, v4
Date: 19 May 2003 20:51:34 -0400 [thread overview]
Message-ID: <1053391893.9507.9.camel@tiny.suse.com> (raw)
In-Reply-To: <20030519163306.4237dab5.rddunlap@osdl.org>
On Mon, 2003-05-19 at 19:33, Randy.Dunlap wrote:
> On Fri, 16 May 2003 16:17:53 -0700 Andrew Morton <akpm@digeo.com> wrote:
>
> | fs/
> | ---
> |
> | - Integrate Chris Mason's 2.4 reiserfs ordered data and data journaling
> | patches. They make reiserfs a lot safer.
>
> What's the delay on this? I used this code last June/July,
> and I understand that SuSE has been shipping it for awhile now.
Mostly because everyone is sick of waiting for me to finish porting and
testing in 2.5. I removed the changes to fs/super.c from my 2.4 code,
the idea is to get submitted to 2.4 so I can lighten my load and work
harder on the 2.5 port.
We'll see, if I don't have it done before ottawa akpm can throw me in
the river. Inclusion is a different story of course but they can't
include it if it isn't fully ported ;-)
-chris
next prev parent reply other threads:[~2003-05-20 0:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 23:17 2.6 must-fix, v4 Andrew Morton
2003-05-16 23:17 ` Andrew Morton
2003-05-17 1:31 ` William Lee Irwin III
2003-05-17 5:16 ` Joseph Fannin
2003-05-17 5:42 ` William Lee Irwin III
2003-05-17 12:34 ` Stuffed Crust
2003-05-17 19:29 ` Felipe Alfaro Solana
2003-05-17 8:05 ` Lars Marowsky-Bree
2003-05-19 23:33 ` Randy.Dunlap
2003-05-20 0:51 ` Chris Mason [this message]
2003-05-16 23:33 ` Greg KH
[not found] <20030516233011$3c2c@gated-at.bofh.it>
[not found] ` <20030516233013$140e@gated-at.bofh.it>
2003-05-18 6:45 ` Andi Kleen
2003-05-18 18:56 ` Geert Uytterhoeven
2003-05-18 6:45 ` Andi Kleen
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=1053391893.9507.9.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.