From: Dave Jones <davej@suse.de>
To: reiserfs-dev@namesys.com
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Resyncing reiserfs changes to 2.5.
Date: Sun, 30 Dec 2001 23:43:33 +0000 [thread overview]
Message-ID: <20011230234333.F16788@suse.de> (raw)
Folks,
The forward ported changes from 2.4 -> 2.5 for reiserfs
in my tree are nearly entirely hand merged by myself.
Whilst I've tested them with no problems, I'd prefer that
some of the reiserfs guys take a look at what I've done to
make sure I've not screwed up something obscure before I start
pushing this to Linus.
Jumbo patch as always is at...
http://www.codemonkey.org.uk/patches/2.5/patch-2.5.1-dj9.diff.bz2
regards,
Dave.
--
Dave Jones. http://www.codemonkey.org.uk
SuSE Labs.
reply other threads:[~2001-12-30 23:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011230234333.F16788@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox