From: Xose Vazquez Perez <xose@wanadoo.es>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: htree for 2.4 ext[23]
Date: Mon, 02 Jun 2003 01:14:58 +0200 [thread overview]
Message-ID: <3EDA88F2.9060105@wanadoo.es> (raw)
Andreas Dilger wrote:
> On Jun 01, 2003 15:17 +0400, Paul P Komkoff Jr wrote:
>> Anybody have working backport of these ?
>>
>> Stuff available at http://thunk.org/tytso/linux/extfs-2.4-update/ IS a)
>> outdated b) gives unpredictable results (e.g. eating filesystems)
>
> Yes, we have a working set of patches for 2.4.20 and a few other kernels
> in our CVS repository. However, these are just taken from Ted's ext3 BK
> repository (I don't think we changed them at all).
>
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lustre/lustre/kernel_patches/patches/Attic/ext-2.4-patch-1.patch?rev=1.1.6.1&only_with_tag=b_devel
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lustre/lustre/kernel_patches/patches/Attic/ext-2.4-patch-2.patch?rev=1.1.6.1&only_with_tag=b_devel
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lustre/lustre/kernel_patches/patches/Attic/ext-2.4-patch-3.patch?rev=1.1.6.1&only_with_tag=b_devel
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lustre/lustre/kernel_patches/patches/Attic/ext-2.4-patch-4.patch?rev=1.1.6.1&only_with_tag=b_devel
what is about mingo patches?
http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/
are same than tytso?
regards,
--
Software is like sex, it's better when it's bug free.
next reply other threads:[~2003-06-01 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 23:14 Xose Vazquez Perez [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 11:17 htree for 2.4 ext[23] Paul P Komkoff Jr
2003-06-01 22:34 ` Andreas Dilger
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=3EDA88F2.9060105@wanadoo.es \
--to=xose@wanadoo.es \
--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