From: John Emmas <john@creativepost.co.uk>
To: pthreads-win32@sourceware.org
Subject: Re: Allocating a thread to a specific processor core
Date: Mon, 14 May 2018 14:09:00 -0000 [thread overview]
Message-ID: <6f61e07b-a26b-cdfa-18bb-67b01daac5ef@creativepost.co.uk> (raw)
In-Reply-To: <qxvlqlv1yqv52vkr5bf8rleh.1526293769816@email.android.com>
On 14/05/2018 11:29, ross.johnson wrote:
>
> I notice your question came via the old Red Hat sourceware repository
> mailing list. The project moved to sourceforge several years ago.
>
> The current head revision at
>
> https://sourceforge.net/p/pthreads4w/wiki/Home/
>
Thanks Ross - after I posted this morning, I realised there's only been
one or two posts here since 2013! So I figured it must have moved
somewhere.
Having said that... the above home page states that there's no mailing
list on Sourceforge yet. So is there one somewhere else?
John
next prev parent reply other threads:[~2018-05-14 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 10:29 ross.johnson
2018-05-14 14:09 ` John Emmas [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-14 8:08 John Emmas
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=6f61e07b-a26b-cdfa-18bb-67b01daac5ef@creativepost.co.uk \
--to=john@creativepost.co.uk \
--cc=pthreads-win32@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).