From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: sct@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: ext3 0.9.10 for Alan's tree
Date: 02 Oct 2001 01:24:31 -0400 [thread overview]
Message-ID: <1002000273.865.13.camel@phantasy> (raw)
In-Reply-To: <3BB946B4.C7479C16@zip.com.au>
In-Reply-To: <1001989916.2780.61.camel@phantasy> <3BB946B4.C7479C16@zip.com.au>
On Tue, 2001-10-02 at 00:46, Andrew Morton wrote:
> Yes, sorry. It's turning out to be a lot of work keeping the master
> ext3 tree in sync with two (rather different) kernels, and running around
> after all the changes which are happening in (ahem) one of them.
Don't explain that -- I know :) I think all of us are wanting a
single-tree development kernel about now...
> We prefer to test a lot before releasing, and the one time I skipped
> that step was for 2.4.10, and it was the one which is broken. Sigh.
>
> Rob, I've added this patch to the download site for interested parties
> to use. http://www.uow.edu.au/~andrewm/linux/ext3/
Great.
> But for a merge with Alan we do have a few more changes backed up,
> and some more testing must be done. I'll try to prepare 0.9.11
> for -ac this week. I'm inclined to down-tools on Linus kernels
> for a while, wait for things to settle down there.
I'll be happy to test and do anything else I can. Thanks for the reply
and all.
> Thanks!
You are welcome :)
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-10-02 5:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 2:31 ext3 0.9.10 for Alan's tree Robert Love
2001-10-02 4:46 ` Andrew Morton
2001-10-02 5:24 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-02 6:06 =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-10-02 6:11 ` Andrew Morton
2001-10-02 7:07 ` David Hollister
2001-10-02 7:28 sayamindu dasgupta
2001-10-02 18:08 ` Mike Fedyk
2001-10-02 18:36 ` John Alvord
2001-10-02 18:45 ` Alan Cox
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=1002000273.865.13.camel@phantasy \
--to=rml@tech9.net \
--cc=akpm@zip.com.au \
--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 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.