From: Petr Baudis <pasky@suse.cz>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] daemon.c: squelch error message from EINTR
Date: Thu, 4 Aug 2005 22:29:57 +0200 [thread overview]
Message-ID: <20050804202957.GD24479@pasky.ji.cz> (raw)
In-Reply-To: <7voe8fk0dq.fsf@assigned-by-dhcp.cox.net>
Dear diary, on Wed, Aug 03, 2005 at 08:20:01AM CEST, I got a letter
where Junio C Hamano <junkio@cox.net> told me that...
> I am not sure if this is the right fix, and I have not received
> an answer from the original author of the patch. I would
> appreciate help from the folks on the list who are familiar with
> the networking.
I think it's fine. EINTR means it got a signal while waiting, it might
be worthwhile checking by strace what signal it actually was - one thing
coming on my mind is SIGPIPE or so, but I barely saw the code. Anyway,
just sticking your hand in sand if you see this is probably fine.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
If you want the holes in your knowledge showing up try teaching
someone. -- Alan Cox
prev parent reply other threads:[~2005-08-04 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 6:20 [PATCH] daemon.c: squelch error message from EINTR Junio C Hamano
2005-08-04 20:29 ` Petr Baudis [this message]
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=20050804202957.GD24479@pasky.ji.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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