From: Scott James Remnant <scott@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Good news for threading!
Date: Tue, 26 May 2009 07:03:31 +0000 [thread overview]
Message-ID: <1243321411.5700.0.camel@wing-commander> (raw)
In-Reply-To: <4A1AA131.7000202@tuffmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Mon, 2009-05-25 at 14:46 +0100, Alan Jenkins wrote:
> I solved one of the reservations that held me back on threaded udevd. I
> still have some other concerns to work on, but I'm feeling much more
> optimistic now.
>
Are you maintaining a GIT tree of your threading work? I'd be very
interested in playing <g>
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-05-26 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 13:46 Good news for threading! Alan Jenkins
2009-05-25 19:09 ` Kay Sievers
2009-05-25 20:28 ` Alan Jenkins
2009-05-25 23:52 ` Kay Sievers
2009-05-26 7:03 ` Scott James Remnant [this message]
2009-05-26 9:32 ` Alan Jenkins
2009-05-26 9:36 ` Alan Jenkins
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=1243321411.5700.0.camel@wing-commander \
--to=scott@ubuntu.com \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).