From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Sending bug reports without setting up email
Date: Wed, 20 Jul 2016 15:29:18 +0200 [thread overview]
Message-ID: <m3shv44evl.fsf@gnus.org> (raw)
In-Reply-To: <6a51f3f7-b6e5-94e8-3b6d-0dd2efe345ed@cs.ucla.edu> (Paul Eggert's message of "Tue, 10 May 2016 08:02:20 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 05/09/2016 11:19 AM, Lars Ingebrigtsen wrote:
>> That is, put the check for res_init back again. Would that be OK?
>
> It should be OK to put the res_init check back into
> configure.ac. However, res_init is not thread-safe, and other threads
> might be doing name resolution. Shouldn't Emacs use res_ninit instead?
Yes, res_ninit would be better, I think. But is res_ninit supported
less/more than res_init on non-GNU/Linux systems, I wonder? I tried
googling for this briefly, but was unable to say...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-07-20 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 13:50 Sending bug reports without setting up email Lars Ingebrigtsen
2016-05-09 18:19 ` Lars Ingebrigtsen
2016-05-09 18:52 ` Eli Zaretskii
2016-05-09 19:03 ` Lars Ingebrigtsen
2016-05-10 15:02 ` Paul Eggert
2016-05-11 20:55 ` daniel sutton
2016-05-11 21:00 ` Kaushal Modi
2016-05-11 21:05 ` Eli Zaretskii
2016-05-11 21:17 ` Kaushal Modi
2016-05-12 5:47 ` Eli Zaretskii
2016-05-11 21:01 ` Eli Zaretskii
2016-07-20 13:29 ` Lars Ingebrigtsen [this message]
2016-07-20 15:01 ` Paul Eggert
2016-07-20 15:06 ` Lars Ingebrigtsen
2016-07-20 16:07 ` Paul Eggert
2016-07-20 16:10 ` Lars Ingebrigtsen
2016-07-20 16:27 ` Paul Eggert
2016-07-20 16:30 ` Lars Ingebrigtsen
2016-07-20 16:37 ` Stefan Monnier
2016-07-21 10:45 ` Lars Ingebrigtsen
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=m3shv44evl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.