From: Andreas Gruenbacher <agruen@suse.de>
To: Nathan Scott <nathans@sgi.com>, Dave Kleikamp <shaggy@austin.ibm.com>
Cc: acl-devel@bestbits.at, linux-fsdevel@vger.kernel.org,
Luka Renko <luka.renko@hermes.si>
Subject: Re: JFS extended attributes and ACLs - New Patches
Date: Fri, 13 Sep 2002 11:27:53 +0200 [thread overview]
Message-ID: <200209131127.53667.agruen@suse.de> (raw)
In-Reply-To: <20020913050640.GC532@frodo>
On Friday 13 September 2002 07:06, Nathan Scott wrote:
> hi Dave,
>
> On Thu, Sep 12, 2002 at 12:34:29PM -0500, Dave Kleikamp wrote:
> > On Thursday 12 September 2002 12:04, Andreas Gruenbacher wrote:
> > > Can you implement the `os2.' namespace in the JFS patches? I'd be
> > > much happier with the patch.
> >
> > I believe I can. I will use the 'os2.' prefix externally, but store it
> > without the prefix. On the other side, any attribute that doesn't
> > begin with a known prefix will get 'os2.' prepended when listing the
> > xattrs.
Good. The namespace should still be flat, as Nathan said already. Which is
what I think you had in mind anyway.
--Andreas.
next prev parent reply other threads:[~2002-09-13 9:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 7:40 JFS extended attributes and ACLs - New Patches Luka Renko
2002-09-12 15:13 ` Andreas Gruenbacher
2002-09-12 16:16 ` Dave Kleikamp
2002-09-12 17:04 ` Andreas Gruenbacher
2002-09-12 17:34 ` Dave Kleikamp
2002-09-13 5:06 ` Nathan Scott
2002-09-13 9:27 ` Andreas Gruenbacher [this message]
2002-09-13 12:18 ` Dave Kleikamp
2002-09-13 13:20 ` [Acl-Devel] " Andreas Gruenbacher
2002-09-13 13:33 ` Dave Kleikamp
2002-09-13 9:32 ` Andreas Gruenbacher
[not found] <Pine.LNX.4.33.0209061703200.26258-100000@wotan.suse.de>
[not found] ` <200209061718.59114.agruen@suse.de>
2002-09-09 14:58 ` Dave Kleikamp
2002-09-09 15:02 ` Andreas Gruenbacher
2002-09-09 15:28 ` Dave Kleikamp
2002-09-09 15:30 ` Dave Kleikamp
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=200209131127.53667.agruen@suse.de \
--to=agruen@suse.de \
--cc=acl-devel@bestbits.at \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luka.renko@hermes.si \
--cc=nathans@sgi.com \
--cc=shaggy@austin.ibm.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.