From: Paul Jackson <pj@sgi.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: Robust futexes
Date: Sat, 18 Feb 2006 20:11:26 -0800 [thread overview]
Message-ID: <20060218201126.7dd9f1e2.pj@sgi.com> (raw)
In-Reply-To: <1140234812.2418.13.camel@localhost.localdomain>
> As an added bonus, the tone of the first response I received (not
> yours!) reminded me why I am not subscribed to lkml...
Oh dear. Now I have on my conscious reminding Rusty why
he keeps off lkml.
I'm not sure quite how I did that, but I wish I hadn't.
I for one found your lkml posts, Rusty, to be delightful.
Take good care of yourself, Rusty.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-02-19 4:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 4:57 Robust futexes Rusty Russell
2006-02-17 6:42 ` Paul Jackson
2006-02-17 7:12 ` Rusty Russell
2006-02-17 7:29 ` Paul Jackson
2006-02-17 9:13 ` Ingo Molnar
2006-02-18 3:53 ` Rusty Russell
2006-02-19 4:11 ` Paul Jackson [this message]
2006-02-20 9:06 ` Ingo Molnar
2006-02-20 22:33 ` Paul Jackson
2006-02-17 15:47 ` Daniel Walker
2006-02-17 16:23 ` Darren Hart
2006-03-09 23:17 ` Rusty Russell
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=20060218201126.7dd9f1e2.pj@sgi.com \
--to=pj@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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