From: Laurent Riffard <laurent.riffard@free.fr>
To: Christian Trefzer <ctrefzer@gmx.de>
Cc: reiserfs-list@namesys.com
Subject: Re: [PATCH] Reiser4 for 2.6.21-rc1
Date: Wed, 07 Mar 2007 00:19:17 +0100 [thread overview]
Message-ID: <45EDF6F5.50602@free.fr> (raw)
In-Reply-To: <20070306092107.GA13707@zeus.uziel.local>
Le 06.03.2007 10:21, Christian Trefzer a écrit :
> Hello Laurent,
>
> I've been using reiser4 with compression extensively during the past
> months, and so I followed its development in -mm pretty closely,
> applying reiser4-internal patches to my ancient 2.6.19-rc6-mm2 tree.
> Your patch applies cleanly against current -stable and vanilla kernels,
> nice job! Yet the changelog of the newest -mm patchset yields two new
> patches by Edward Shishkin, which also apply cleanly on top of your
> patch. I've been using them for days now without incident, so I think
> they might be alright ; ) In order to keep these patches unmodified, I
> will attach them both to this e-mail.
Thanks for pointing out these 2 patches. I added them and I just updated
http://laurent.riffard.free.fr/reiser4/reiser4-for-2.6.20 and
http://laurent.riffard.free.fr/reiser4/reiser4-for-2.6.21-rc1.
--
laurent
next prev parent reply other threads:[~2007-03-06 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 20:28 [PATCH] Reiser4 for 2.6.21-rc1 Laurent Riffard
2007-03-02 20:35 ` Laurent Riffard
2007-03-05 17:20 ` Nicolas STRANSKY
2007-03-05 21:21 ` Laurent Riffard
2007-03-06 16:34 ` Edward Shishkin
2007-03-08 12:17 ` reiser4 panic in do_readpage_extent Devils-Hawk
2007-03-09 1:17 ` Edward Shishkin
2007-03-09 20:36 ` Edward Shishkin
2007-03-09 21:15 ` Devils-Hawk
2007-03-11 13:49 ` Edward Shishkin
[not found] ` <20070306092107.GA13707@zeus.uziel.local>
2007-03-06 23:19 ` Laurent Riffard [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-03 11:24 [PATCH] Reiser4 for 2.6.21-rc1 Laurent Riffard
2007-03-03 12:25 laurent.riffard
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=45EDF6F5.50602@free.fr \
--to=laurent.riffard@free.fr \
--cc=ctrefzer@gmx.de \
--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.