From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, akpm@osdl.org,
linux-kernel@vger.kernel.org, cw@f00f.org
Subject: Re: [uml-devel] Re: [patch 09/20] uml: use SIG_IGN for empty sighandler
Date: Fri, 05 Nov 2004 00:48:04 -0500 [thread overview]
Message-ID: <200411050548.iA55m4DZ007773@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 04 Nov 2004 05:11:44 +0100." <200411040511.54892.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> I had a doubt on this, but I was not getting much feedback from you...
Yeah, sorry.
> Also, if you reject this, I'd require a comment-only patch for it: "as
> soon as I remember why" makes me think back to my yesterday's class,
> when the teacher said "put comments in your code or you'll soon
> forget what it does!" 8-O (yes, 1st year University student :-( ).
The thing is, you often don't realize what's going to be mysterious until it
actually is, and then it's too late for the comment :-)
In this case, it wants to be bounced out of sigprocmask when a SIGWINCH
arrives. In order to do so, it must have a handler registered, even if
it does nothing.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-11-05 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 23:17 [uml-devel] [patch 09/20] uml: use SIG_IGN for empty sighandler blaisorblade_spam
2004-11-04 4:51 ` [uml-devel] " Jeff Dike
2004-11-04 4:11 ` Blaisorblade
2004-11-05 5:48 ` Jeff Dike [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=200411050548.iA55m4DZ007773@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.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