From: Andreas Jaeger <aj@suse.de>
To: Ulrich Drepper <drepper@redhat.com>
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: I'll be gone (again)
Date: Sun, 02 Jun 2002 21:53:00 -0000 [thread overview]
Message-ID: <u8d6v97ykw.fsf@gromit.moeb> (raw)
In-Reply-To: <1022818274.13598.255.camel@myware.mynet> (Ulrich Drepper's message of "30 May 2002 21:11:13 -0700")
Ulrich Drepper <drepper@redhat.com> writes:
> [...]
> There are also a few more things:
>
> - the various *xattr syscalls which were introduced in the 2.5 kernel
> might need libc support. I guess they do. But somebody should contact
> whoever wrote the code and ask them about the API which should be
> provided.
>
I'm currently looking into the xattr stuff,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
prev parent reply other threads:[~2002-06-03 4:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 21:11 Ulrich Drepper
2002-06-02 21:53 ` Andreas Jaeger [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=u8d6v97ykw.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).