From: Ulrich Drepper <drepper@cygnus.com>
To: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: anybody handling the LCK64 stuff?
Date: Mon, 13 Dec 1999 09:32:00 -0000 [thread overview]
Message-ID: <m3r9gqg35b.fsf@localhost.localnet> (raw)
Can anybody handle adding the LCK64 stuff? I think it will have to be
similar to the truncate64 code where we fall back on the LCK methods
if the kernel is not supporting it.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next reply other threads:[~1999-12-13 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 9:32 Ulrich Drepper [this message]
1999-12-13 11:30 ` Andreas Jaeger
1999-12-14 1:44 ` Andreas Jaeger
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=m3r9gqg35b.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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).