From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
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: Thu, 4 Nov 2004 05:11:44 +0100 [thread overview]
Message-ID: <200411040511.54892.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200411040451.iA44pJ5G012816@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
On Thursday 04 November 2004 05:51, Jeff Dike wrote:
> blaisorblade_spam@yahoo.it said:
> > Avoid creating a dummy no-op procedure instead of using SIG_IGN.
>
> Andrew, can you hold off on this one?
> I did that on purpose, and as soon
> as I remember why, I'll know whether this patch is good :-)
I had a doubt on this, but I was not getting much feedback from you...
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 other patches are OK by me. Consider them acked.
Very fine.
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-04 4:34 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 [this message]
2004-11-05 5:48 ` Jeff Dike
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=200411040511.54892.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=jdike@addtoit.com \
--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