From: "Dr. Giovanni A. Orlando" <gorlando@futuretg.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
Hans Reiser <reiser@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: When Reiser4 will be officially included in the kernel? ...
Date: Wed, 04 May 2005 19:16:18 +0000 [thread overview]
Message-ID: <42791F82.8080906@futuretg.com> (raw)
In-Reply-To: <1115223159.4741.58.camel@tribesman.namesys.com>
>They were on principle against
>ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/reiser4-allow-drop_inode-implementation.patch
>ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc3/2.6.10-rc3-mm1/broken-out/reiser4-perthread-pages.patch
>ftp://ftp.ru.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc3/2.6.12-rc3-mm2/broken-out/reiser4-export-inode_lock.patch
>
>and few older patches.
>We are currently trying to eliminate the need in
>reiser4-export-inode_lock.patch which is the last of bad patches.
>
>
Hi,
This is OK, however, what I am looking for is to download the Kernel
from kernel.org, and found Reiser4 code inside. This means officially
for me.
Thanks,
Giovanni.
>This one seems to be the hardest to get rid of.
>
>
>
>>James
>>
>>
>>
>
>
>
--
--
--
Check FT Websites ... http://www.futuretg.com - ftp://ftp.futuretg.com
http://www.FTLinuxCourse.com
http://www.FTLinuxCourse.com/Certification
http://www.RPMParadaise.org
http://www.YourPersonalOperatingSystem.com
Mobile: +39 393 665 4239
Lancelot is back!
--
next prev parent reply other threads:[~2005-05-04 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 18:38 When Reiser4 will be officially included in the kernel? Dr. Giovanni A. Orlando
2005-05-04 9:23 ` Vladimir Saveliev
2005-05-04 12:33 ` James Courtier-Dutton
2005-05-04 16:12 ` Vladimir Saveliev
2005-05-04 19:16 ` Dr. Giovanni A. Orlando [this message]
2005-05-04 22:38 ` Re[2]: " Pysiak Satriani
2005-05-05 3:26 ` Valdis.Kletnieks
2005-05-04 13:37 ` Dr. Giovanni A. Orlando
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=42791F82.8080906@futuretg.com \
--to=gorlando@futuretg.com \
--cc=James@superbug.demon.co.uk \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.