From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
Jeff Mahoney <jeffm@suse.com>,
Anders Widman <andewid@tnonline.net>,
reiserfs-list@namesys.com
Subject: Re: Multiple data streams...
Date: 03 Apr 2003 15:09:21 -0500 [thread overview]
Message-ID: <1049400560.15217.1134.camel@tiny.suse.com> (raw)
In-Reply-To: <3E8C90A1.1010305@namesys.com>
On Thu, 2003-04-03 at 14:50, Hans Reiser wrote:
> Chris Mason wrote:
>
> >
> >I know that you were concerned about the v3 acl support being a
> >compatibility problem in v4, but given the acls/xattrs can easily be
> >exported to a neutral format and then reimported into whatever v4
> >supports, I don't think it will be a problem. If it is, we'll work with
> >you to help fix it.
> >
> >
> >
> >
> We will both work to ensure problems are kept small in this area, and I
> think it is best to spend our time coding rather than worrying about
> this when we are not at any decision point in the process. Hopefully
> it will not be substantive as a problem.
Agreed ;-)
-chris
next prev parent reply other threads:[~2003-04-03 20:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 9:28 Multiple data streams Anders Widman
2003-04-02 9:47 ` Anders Widman
2003-04-02 16:43 ` Hans Reiser
2003-04-03 16:49 ` Valdis.Kletnieks
2003-04-02 12:40 ` Russell Coker
2003-04-02 13:08 ` Anders Widman
2003-04-02 21:32 ` Russell Coker
2003-04-03 19:00 ` Hans Reiser
2003-04-03 19:57 ` Russell Coker
2003-04-03 21:53 ` Hans Reiser
2003-04-02 15:18 ` Oleg Drokin
2003-04-02 15:30 ` Alexander G. M. Smith
2003-04-02 16:12 ` Jeff Mahoney
2003-04-02 16:53 ` Hans Reiser
2003-04-02 17:07 ` Chris Mason
2003-04-02 17:13 ` Nikita Danilov
2003-04-03 18:37 ` Hans Reiser
2003-04-03 19:02 ` Chris Mason
2003-04-03 19:50 ` Hans Reiser
2003-04-03 20:09 ` Chris Mason [this message]
2003-04-04 7:41 ` Nikita Danilov
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=1049400560.15217.1134.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=Nikita@Namesys.COM \
--cc=andewid@tnonline.net \
--cc=jeffm@suse.com \
--cc=reiser@namesys.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.