From: Chris Mason <mason@suse.com>
To: reiserfs-list@namesys.com
Subject: [PATCH] finally... data logging for 2.4.20-pre10
Date: 15 Oct 2002 15:24:42 -0400 [thread overview]
Message-ID: <1034709883.5053.920.camel@tiny> (raw)
Hello all,
I've uploaded new data logging code against 2.4.20-pre10 to
ftp.suse.com/pub/people/mason/patches/data-logging/2.4.20
The mirror might take a little while to update.
This code is lightly tested, use with caution for a few days. The
journal relocation patches are not complete yet, I haven't integrated
them with the new options parsing code in 2.4.20-pre, so you can't pass
-o jdev= when mounting the FS.
Aside from merging into the latest kernel, there are a few bug fixes for
corner case oopsen hit during suse testing.
-chris
next reply other threads:[~2002-10-15 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 19:24 Chris Mason [this message]
2002-10-15 22:16 ` [PATCH] finally... data logging for 2.4.20-pre10 Manuel Krause
2002-10-18 13:41 ` Manuel Krause
2002-10-23 19:01 ` John Dalbec
2002-10-23 21:59 ` Manuel Krause
2002-10-24 12:51 ` John Dalbec
2002-10-24 13:12 ` Chris Mason
2002-11-12 15:39 ` Toby Dickenson
2002-11-18 14:31 ` John Dalbec
-- strict thread matches above, loose matches on Subject: below --
2002-10-15 22:29 JP Howard
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=1034709883.5053.920.camel@tiny \
--to=mason@suse.com \
--cc=reiserfs-list@namesys.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.