From: Pedro Alves <palves@redhat.com>
To: Roland Schwingel <roland@onevision.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH v3] Add dll trampoline code handling for windows 64bit
Date: Fri, 30 Mar 2012 09:15:00 -0000 [thread overview]
Message-ID: <4F75795B.9000801@redhat.com> (raw)
In-Reply-To: <4F7556D4.4010404@onevision.com>
On 03/30/2012 07:46 AM, Roland Schwingel wrote:
> The other 2 formatting I will also correct on commit. But if you want I am doing
> a 4th version of my patch with your suggested changes and send it in. Elsewise I will
> sit and wait until my assignment stuff gets done and commit it later on and avoid unneccessary noise.
Please send an updated patch, so we have in the archives the exact patch as what is
checked in, and in case some other maintainer wants to take a look, best have him look at
the refreshed patch. In fact, if you had sent it already in that email, there'd have been
no extra noise, right? ;-)
--
Pedro Alves
next prev parent reply other threads:[~2012-03-30 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 6:47 Roland Schwingel
2012-03-30 9:15 ` Pedro Alves [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-16 9:56 Roland Schwingel
2012-03-29 18:21 ` Joel Brobecker
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=4F75795B.9000801@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=roland@onevision.com \
/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