All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Jeff Mahoney <jeffm@suse.com>, Jan Kara <jack@suse.cz>,
	ReiserFS List <reiserfs-list@namesys.com>,
	"E. Gryaznova" <grev@namesys.com>
Subject: Re: [PATCH 00/11] reiserfs: xattr rework
Date: Thu, 09 Mar 2006 10:26:46 -0800	[thread overview]
Message-ID: <44107366.5090407@namesys.com> (raw)
In-Reply-To: <20060308231426.GI14934@schatzie.adilger.int>

All of this is why xattrs should not be implemented without first
implementing plugins.:-/

Really guys, there was a reason for my not wanting xattrs to go into
V3.  Do you see it now?  This is what happens when marketing determines
feature ship schedules.  You could implement this xattr stuff in V4 in
1/5th the time, 5 times the performance, and twice the elegance.   Of
course, implementing them as pseudo files would be far more elegant
still....

Hans

  reply	other threads:[~2006-03-09 18:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 20:14 [PATCH 00/11] reiserfs: xattr rework Jeff Mahoney
2006-03-01 12:34 ` Jan Kara
2006-03-02 21:53   ` Jeff Mahoney
2006-03-03  0:29     ` Jan Kara
2006-03-03  0:56       ` Jeff Mahoney
2006-03-03 10:04         ` Jan Kara
2006-03-03 22:17           ` Jeff Mahoney
2006-03-06 11:59             ` Jan Kara
2006-03-07 21:39               ` Jeff Mahoney
2006-03-08 18:20                 ` Jan Kara
2006-03-08 19:12                   ` Jeff Mahoney
2006-03-08 23:14                     ` Andreas Dilger
2006-03-09 18:26                       ` Hans Reiser [this message]
2006-03-09 19:11                         ` Jeff Mahoney
2006-03-09 19:52                           ` Hans Reiser

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=44107366.5090407@namesys.com \
    --to=reiser@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=grev@namesys.com \
    --cc=jack@suse.cz \
    --cc=jeffm@suse.com \
    --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.