public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hollister <david@digitalaudioresources.org>
To: "Frédéric L. W. Meunier" <0@pervalidus.net>
Cc: Andrew Morton <akpm@zip.com.au>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 0.9.10 for Alan's tree
Date: Tue, 02 Oct 2001 00:07:14 -0700	[thread overview]
Message-ID: <3BB967A2.7080908@digitalaudioresources.org> (raw)
In-Reply-To: <20011002030655.E249@pervalidus>

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.


Granted, I'm no "power user", but I've been using it for several days now 
without any noticable problem (other than what seems to be a possibly dying hard 
drive... I occasionally get the same errors on 2.4.9 with ext3 and 2.2.19.

-- 
David Hollister
Driversoft Engineering:  http://devicedrivers.com
Digital Audio Resources: http://digitalaudioresources.org


  parent reply	other threads:[~2001-10-02  7:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02  6:06 ext3 0.9.10 for Alan's tree =?unknown-8bit?B?RnLpZOlyaWMgTC4gVy4=?= Meunier
2001-10-02  6:11 ` Andrew Morton
2001-10-02  7:07 ` David Hollister [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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=3BB967A2.7080908@digitalaudioresources.org \
    --to=david@digitalaudioresources.org \
    --cc=0@pervalidus.net \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox