From: christophe barbe <christophe.barbe@ufies.org>
To: linux-kernel@vger.kernel.org
Subject: ext3 oops with 2.4.21 [Was: ext3 oops]
Date: Tue, 22 Jul 2003 07:55:01 -0400 [thread overview]
Message-ID: <20030722115501.GA21051@cattlegrid.net> (raw)
In-Reply-To: <1058836184.29528.3.camel@localhost>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 301 bytes --]
I should have specified that it was with a vanilla 2.4.21 in the title.
Christophe
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
Cats are intented to teach us that not everything in nature has a
function. --Garrison Keillor
prev parent reply other threads:[~2003-07-22 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 1:09 ext3 oops Christophe Barbé
2003-07-22 11:55 ` christophe barbe [this message]
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=20030722115501.GA21051@cattlegrid.net \
--to=christophe.barbe@ufies.org \
--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