From: Mark Kettenis <kettenis@wins.uva.nl>
To: aj@suse.de
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: Bind 8.2 Integration
Date: Wed, 01 Dec 1999 08:25:00 -0000 [thread overview]
Message-ID: <199912011625.RAA02229@landau.wins.uva.nl> (raw)
In-Reply-To: <u8bt8ahc3n.fsf@gromit.rhein-neckar.de>
From: Andreas Jaeger <aj@suse.de>
Date: 01 Dec 1999 17:14:52 +0100
I've avoided the res_sendsigned/res_nsendsigned interfaces completly
(and also the resfindzonecut interface). This means that the
resulting libresolv can not be used by named, nslookup or dig. But it
can be used instead of the old libresolv and we can export it.
Although I think that we should try to privide all functions in
<resolv.h> this is probably a good idea for now. We can always add
those functions when people start compaining. Removing them would be
a bigger problem.
Mark
next prev parent reply other threads:[~1999-12-01 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-26 4:50 Andreas Jaeger
1999-11-26 5:34 ` Mark Kettenis
1999-12-01 8:15 ` Andreas Jaeger
1999-12-01 8:25 ` Mark Kettenis [this message]
1999-12-03 6:55 ` 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=199912011625.RAA02229@landau.wins.uva.nl \
--to=kettenis@wins.uva.nl \
--cc=aj@suse.de \
--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).