From: Kai Tietz <ktietz70@googlemail.com>
To: Ross Johnson <Ross.Johnson@homemail.com.au>
Cc: pthreads-win32@sourceware.org
Subject: Re: [patch] Support for x64 Windows
Date: Mon, 22 Jun 2009 08:43:00 -0000 [thread overview]
Message-ID: <90baa01f0906220143q3fd63245x8f8980b338cc601@mail.gmail.com> (raw)
In-Reply-To: <4A3F4356.2070202@homemail.com.au>
2009/6/22 Ross Johnson <Ross.Johnson@homemail.com.au>:
> Kai Tietz wrote:
>>
>> PING?
>>
>
> PONG :-)
>
> I don't have the technology to confirm the patch with a build and run, but I
> will run an eye over it ASAP.
>
> Regards.
> Ross
>
Thanks, if you need tests or assistant, don't hesitate to ask me, or
visit our IRC channel on irc://irc.oftc.net/mingw-w64
Regards,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
next prev parent reply other threads:[~2009-06-22 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 20:19 Kai Tietz
2009-06-22 7:36 ` Kai Tietz
2009-06-22 8:40 ` Ross Johnson
2009-06-22 8:43 ` Kai Tietz [this message]
2009-08-12 8:24 ` Kai Tietz
2010-02-14 14:56 ` Michel
2009-09-12 10:46 xxcv
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=90baa01f0906220143q3fd63245x8f8980b338cc601@mail.gmail.com \
--to=ktietz70@googlemail.com \
--cc=Ross.Johnson@homemail.com.au \
--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).