From: evilninja <evilninja@gmx.net>
To: reiserfs-list@namesys.com
Cc: Christian Mayrhuber <christian.mayrhuber@gmx.net>
Subject: Re: Reiserfs kernel config description outdated
Date: Fri, 19 Nov 2004 01:12:07 +0100 [thread overview]
Message-ID: <419D3A57.8020701@gmx.net> (raw)
In-Reply-To: <200411161332.00722.christian.mayrhuber@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
Christian Mayrhuber wrote:
> I think the sentence "Additional patches are needed
> for NFS and quotas, please see <http://www.namesys.com/> for links."
> should be dropped in 2.6.
maybe the patch could go in....?
--
BOFH excuse #182:
endothermal recalibration
[-- Attachment #2: reiserfs-2.6_minor-doc-fix.patch --]
[-- Type: text/plain, Size: 921 bytes --]
--- linux-2.6/fs/Kconfig 2004-11-10 14:15:25.000000000 +0100
+++ linux-2.6/fs/Kconfig.edited 2004-11-19 01:05:38.000000000 +0100
@@ -170,14 +170,13 @@
architectural foundations.
In general, ReiserFS is as fast as ext2, but is very efficient with
- large directories and small files. Additional patches are needed
- for NFS and quotas, please see <http://www.namesys.com/> for links.
+ large directories and small files.
It is more easily extended to have features currently found in
database and keyword search systems than block allocation based file
systems are. The next version will be so extended, and will support
- plugins consistent with our motto ``It takes more than a license to
- make source code open.''
+ plugins consistent with our motto "It takes more than a license to
+ make source code open."
Read <http://www.namesys.com/> to learn more about reiserfs.
prev parent reply other threads:[~2004-11-19 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 12:32 Reiserfs kernel config description outdated Christian Mayrhuber
2004-11-19 0:12 ` evilninja [this message]
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=419D3A57.8020701@gmx.net \
--to=evilninja@gmx.net \
--cc=christian.mayrhuber@gmx.net \
--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.