From: Stan Shebs <stan@codesourcery.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v2 - part 0)
Date: Thu, 13 Nov 2008 21:41:00 -0000 [thread overview]
Message-ID: <491C6C09.4050300@codesourcery.com> (raw)
In-Reply-To: <406742BB-4F37-406B-B4E3-75C8DD2DBD03@adacore.com>
Tristan Gingold wrote:
>
> On Nov 13, 2008, at 3:52 PM, Mark Kettenis wrote:
>>> is there any remaining work to do before getting the approval ?
>>
>> Hmm, it seems something (you?) keeps spamming the lists with v2 of the
>> diff whereas I thought you already had a v3 diff. I'm afraid I
>> completely lost track of what is what.
>
> Although there might be something wrong here, I don't see these mails
> in the archives.
> Can you sent me privately these spams ? We will try to fix that.
I think it's just that you updated some parts to v3, while others are
still at v2. When I sorted my mailbox by sender, it became much clearer.
There's nothing wrong, it's just that you've been so responsive that
there's not the usual multi-week gap between one rev of the patch and
the next. :-)
Anyway, I'm the most logical reviewer for the bulk of native support,
I'll give you some feedback in the next few days. In the meantime,
please run the testsuite, let's see what the basic numbers are looking like.
Stan
next prev parent reply other threads:[~2008-11-13 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 10:14 Tristan Gingold
2008-11-13 15:11 ` Tristan Gingold
2008-11-13 19:41 ` Mark Kettenis
2008-11-13 20:40 ` Tristan Gingold
2008-11-13 21:41 ` Stan Shebs [this message]
2008-11-14 16:28 ` Tristan Gingold
2008-11-14 16:41 ` Stan Shebs
2008-11-14 17:04 ` Eli Zaretskii
2008-11-14 17:44 ` Tristan Gingold
2008-11-14 17:40 ` Joel Brobecker
2008-11-14 17:47 ` Mark Kettenis
2008-11-14 15:51 ` Eli Zaretskii
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=491C6C09.4050300@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=mark.kettenis@xs4all.nl \
/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