From: Michael Albinus <michael.albinus@gmx.de>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
16026@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#16026: Gnus shouldn't use old connections
Date: Tue, 31 Jan 2017 17:26:08 +0100 [thread overview]
Message-ID: <87h94fqjq7.fsf@gmx.de> (raw)
In-Reply-To: <87r33jnvn1.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 31 Jan 2017 09:37:06 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
Hi Ted,
> It's easy to create an ad-hoc system just for network timeout
> parameters, like I did with many GnuTLS parameters early on, but the
> systematic approach Michael gave us is much better. The only reason I
> haven't implemented it is lack of time.
If I could help, just ping me. Not that I have too much free time, but
I'm interested in this.
> Ted
Best regards, Michael.
next prev parent reply other threads:[~2017-01-31 16:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7856.1385996719.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.7856.1385996719.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-12-02 15:19 ` bug#16026: Gnus shouldn't use old connections Sebastien Vauban
2013-12-02 16:12 ` Stefan Monnier
2013-12-04 16:04 ` Ted Zlatanov
2017-01-25 16:55 ` Lars Ingebrigtsen
2017-01-25 18:26 ` Stefan Monnier
2017-01-30 20:12 ` Ted Zlatanov
2017-01-30 22:38 ` Stefan Monnier
2017-01-31 14:37 ` Ted Zlatanov
2017-01-31 16:26 ` Michael Albinus [this message]
2017-02-02 3:43 ` bug#16026: Connection specific settings and proxies Lars Ingebrigtsen
2017-02-02 14:46 ` Ted Zlatanov
2017-02-02 23:58 ` Daniel McClanahan
[not found] ` <87o9ykr6os.fsf@flea>
2017-02-03 15:37 ` Michael Albinus
2017-02-06 15:22 ` Ted Zlatanov
[not found] ` <87k293ny36.fsf@flea>
2017-02-12 17:42 ` Michael Albinus
[not found] ` <87d1enz4p2.fsf@gmx.de>
2017-02-20 16:01 ` Lars Ingebrigtsen
2013-12-02 15:03 bug#16026: Gnus shouldn't use old connections Stefan Monnier
2013-12-02 15:53 ` Leo Liu
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=87h94fqjq7.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=16026@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=tzz@lifelogs.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.
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).