From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] fix conv_lisp_to_sockaddr for AF_INET6 addresses
Date: Mon, 08 Feb 2016 05:34:11 +0200 [thread overview]
Message-ID: <83io1zri30.fsf@gnu.org> (raw)
In-Reply-To: <87egco56s6.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 08 Feb 2016 12:29:13 +1100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 08 Feb 2016 12:29:13 +1100
>
> John Wiegley <jwiegley@gmail.com> writes:
>
> > 2. We need a suite of tests for this feature, because it makes a rather
> > fundamental change, and I'd like some coverage to ensure that others
> > working in similar areas won't break it in future.
>
> Sure. Network tests have to be done locally though, right? I don't
> think we have the infrastructure to set up a TLS server in Emacs, so
> that part is kinda hard to test, but there's a lot of other tests we can
> do with Emacs as both server and client, of course.
Can't something like that be done with Perl or Python, or even (gasp!)
with another copy of Emacs, on the same machine?
next prev parent reply other threads:[~2016-02-08 3:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-06 16:06 [PATCH] fix conv_lisp_to_sockaddr for AF_INET6 addresses David Edmondson
2016-02-07 1:45 ` Lars Ingebrigtsen
2016-02-07 1:50 ` Lars Ingebrigtsen
2016-02-07 17:52 ` John Wiegley
2016-02-08 1:29 ` Lars Ingebrigtsen
2016-02-08 3:34 ` Eli Zaretskii [this message]
2016-02-08 3:59 ` Lars Ingebrigtsen
2016-02-08 4:01 ` Lars Ingebrigtsen
2016-02-08 4:07 ` Lars Ingebrigtsen
2016-02-08 7:03 ` Michael Albinus
2016-02-08 7:26 ` Lars Ingebrigtsen
2016-02-08 17:04 ` Eli Zaretskii
2016-02-08 23:17 ` Lars Ingebrigtsen
2016-02-09 19:13 ` Eli Zaretskii
2016-02-09 23:07 ` Lars Ingebrigtsen
2016-02-10 20:08 ` Eli Zaretskii
2016-02-10 20:31 ` Eli Zaretskii
2016-02-11 3:54 ` Lars Ingebrigtsen
2016-02-13 13:19 ` Eli Zaretskii
2016-02-08 3:43 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83io1zri30.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).