From: Marco Trudel <mtrudel@gmx.ch>
To: Keith Seitz <keiths@redhat.com>,
Java Patch List <java-patches@gcc.gnu.org>
Subject: Re: [RFA] Add JDWP VM_INIT JVMTI callback
Date: Fri, 19 Jan 2007 18:18:00 -0000 [thread overview]
Message-ID: <45B10B77.8000307@gmx.ch> (raw)
In-Reply-To: <45B108EF.2070601@redhat.com>
I sent this to the patches list as well. I assume Keith just hit the
wrong button in the mail application:
Keith Seitz wrote:
> Marco Trudel wrote:
>
>>> Keith> Ugh, you know, and I really WAS being careful about that... I
>>> Keith> double-checked that all my functions did that -- all the JVMTI
>>> ones,
>>> Keith> at least. Sigh.
>
> And starting today, I'm turning a new leaf. Before I commit any patch, I
> will verify that it builds with a linux-mingw32 cross compiler. [Okay,
> actually, starting later today when it "finishes" building.]
I don't know if thats a good solution. I'm sure you can use your time
better than that. What about a regularly cross-compilation session where
error reports are sent to the list and the responsible guys try to fix
problems? No, not that a good idea I guess...
Marco
next prev parent reply other threads:[~2007-01-19 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 6:40 Keith Seitz
2007-01-16 19:38 ` Tom Tromey
2007-01-16 19:54 ` Keith Seitz
2007-01-19 0:00 ` Marco Trudel
2007-01-19 0:03 ` Keith Seitz
2007-01-19 15:37 ` Tom Tromey
2007-01-19 17:56 ` Marco Trudel
2007-01-19 18:11 ` David Daney
2007-01-19 18:23 ` Marco Trudel
2007-01-19 18:35 ` David Daney
[not found] ` <45B108EF.2070601@redhat.com>
2007-01-19 18:18 ` Marco Trudel [this message]
2007-01-20 0:02 ` Tom Tromey
2007-01-20 12:28 ` Marco Trudel
2007-01-20 18:33 ` Tom Tromey
2007-01-19 0:05 ` Andrew Haley
2007-01-19 1:31 ` Keith Seitz
2007-01-19 15:40 ` Tom Tromey
2007-01-19 17:27 ` Keith Seitz
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=45B10B77.8000307@gmx.ch \
--to=mtrudel@gmx.ch \
--cc=java-patches@gcc.gnu.org \
--cc=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).