unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rpluim@gmail.com
Cc: 21337-done@debbugs.gnu.org
Subject: bug#21337: 25.0.50; inotify error message
Date: Sat, 05 Sep 2015 11:38:56 +0300	[thread overview]
Message-ID: <83613p8dlr.fsf@gnu.org> (raw)
In-Reply-To: <834mjj4k2f.fsf@gnu.org>

> Date: Fri, 28 Aug 2015 16:30:16 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 21337@debbugs.gnu.org
> 
> > From: Robert Pluim <rpluim@gmail.com>
> > Cc: 21337@debbugs.gnu.org
> > Date: Wed, 26 Aug 2015 19:02:23 +0200
> > 
> > Step 5 should never happen, but because step 2 did not clear the
> > Available fd_set, and the HAVE_GNUTLS code incremented nfds, we think
> > there's data to be read.
> > 
> > The following patch, which zeros out Available when the GNUTLS code
> > does its thing has fixed things for me. I've convinced myself it has
> > no bad side-effects, but would appreciate a second opinion, especially
> > since the option also exists to just zero out Available
> > unconditionally when nfds==0.
> 
> Thanks for the investigation and the patch.  If no one objects in a
> few days, I will commit your changes.

Done.





  reply	other threads:[~2015-09-05  8:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 12:12 bug#21337: 25.0.50; inotify error message Robert Pluim
2015-08-24 15:52 ` Eli Zaretskii
2015-08-24 16:22   ` Robert Pluim
2015-08-24 16:34     ` Eli Zaretskii
2015-08-24 16:51       ` Robert Pluim
2015-08-24 17:18         ` Eli Zaretskii
2015-08-24 18:32           ` Robert Pluim
2015-08-24 19:36             ` Eli Zaretskii
2015-08-26 17:02               ` Robert Pluim
2015-08-28 13:30                 ` Eli Zaretskii
2015-09-05  8:38                   ` Eli Zaretskii [this message]
2015-09-07  7:21                 ` Tassilo Horn
2015-09-07  7:43                   ` Robert Pluim
2015-09-07 15:01                     ` Eli Zaretskii
2015-09-07 15:15                       ` Robert Pluim
2015-09-09 16:49                         ` Tassilo Horn
2015-09-09 17:57                           ` Eli Zaretskii

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=83613p8dlr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=21337-done@debbugs.gnu.org \
    --cc=rpluim@gmail.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).