From: John Alvord <jalvo@mbay.net>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 0.9.10 for Alan's tree
Date: Tue, 02 Oct 2001 11:36:09 -0700 [thread overview]
Message-ID: <562krt8uk7hml11k4741kuqlbsqa53hqbn@4ax.com> (raw)
In-Reply-To: <F295R5VX9q2TwOk6AIe0000f57a@hotmail.com> <20011002110825.A1012@mikef-linux.matchmail.com>
In-Reply-To: <20011002110825.A1012@mikef-linux.matchmail.com>
On Tue, 2 Oct 2001 11:08:25 -0700, Mike Fedyk <mfedyk@matchmail.com>
wrote:
>On Tue, Oct 02, 2001 at 07:28:34AM +0000, sayamindu dasgupta wrote:
>> Fr?d?ric L. W. Meunier wrote:
>>
>> >Andrew Morton wrote:
>> >
>> >
>> >>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.
>> >>
>> >
>> >How broken ? I ask because I'm worried since I use it. Or
>> >it's just the compilation problem with CONFIG_BUFFER_DEBUG
>> >and nothing serious ?
>> >
>> >PS: I don't see any other reports on ext3-users.
>>
>> hello
>> i've been using it for a few weeks and i don't get any probs
>> cheers
>> Sayamindu
>
>I don't think so...
>
>2.4.10-pre11 was only released ~1 week ago...
>
Wasn't there a big deal about having a common journalling service
before other journalling systems jumped into the pool?
john
next prev parent reply other threads:[~2001-10-02 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 7:28 sayamindu dasgupta
2001-10-02 18:08 ` Mike Fedyk
2001-10-02 18:36 ` John Alvord [this message]
2001-10-02 18:45 ` Alan Cox
-- 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 2:31 Robert Love
2001-10-02 4:46 ` Andrew Morton
2001-10-02 5:24 ` Robert Love
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=562krt8uk7hml11k4741kuqlbsqa53hqbn@4ax.com \
--to=jalvo@mbay.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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
all inboxes | Powered by JetHome®