From: Christoph Hellwig <hch@infradead.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Christoph Hellwig <hch@infradead.org>,
531950-quiet@bugs.debian.org, Nathan Scott <nscott@aconex.com>,
Petr Salinger <Petr.Salinger@seznam.cz>,
xfs@oss.sgi.com
Subject: Re: Bug#531950: attr: FTBFS on GNU/kFreeBSD
Date: Mon, 15 Jun 2009 05:42:44 -0400 [thread overview]
Message-ID: <20090615094244.GA4793@infradead.org> (raw)
In-Reply-To: <20090614205628.GB25535@hall.aurel32.net>
On Sun, Jun 14, 2009 at 10:56:28PM +0200, Aurelien Jarno wrote:
> Would such a patch be accepted more easily than the ENODATA patch?
I don't think it's an except but in addition. Wherever we do a strerror
in the attr code we will have to special case ENODATA on Linux and only
there. Independent of that I think we would better of using the raw
syscalls in platforms already using binary namespaces rather than double
translation. Note that this is only applicable for the IRIX-heritage
attr_* routines exports by libattr, not the *xattr routines it also
exports.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-15 9:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1450746396.6081061244543230576.JavaMail.root@mail-au.aconex.com>
2009-06-09 10:31 ` Bug#531950: attr: FTBFS on GNU/kFreeBSD Nathan Scott
2009-06-09 11:35 ` Petr Salinger
2009-06-09 12:10 ` Christoph Hellwig
2009-06-14 16:35 ` Aurelien Jarno
2009-06-14 20:33 ` Christoph Hellwig
2009-06-14 20:56 ` Aurelien Jarno
2009-06-15 9:42 ` Christoph Hellwig [this message]
2009-06-15 10:26 ` Petr Salinger
2009-06-15 10:05 ` Aurelien Jarno
2009-06-19 15:37 ` Andreas Gruenbacher
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=20090615094244.GA4793@infradead.org \
--to=hch@infradead.org \
--cc=531950-quiet@bugs.debian.org \
--cc=Petr.Salinger@seznam.cz \
--cc=aurelien@aurel32.net \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox