From: Mark Wielaard <mark@klomp.org>
To: tromey@redhat.com
Cc: java-patches@gcc.gnu.org
Subject: Re: RFC: Enabling Corba
Date: Sat, 26 Nov 2005 00:53:00 -0000 [thread overview]
Message-ID: <1132966208.5509.140.camel@localhost.localdomain> (raw)
In-Reply-To: <17287.25017.275586.986725@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 420 bytes --]
Hi Tom,
On Fri, 2005-11-25 at 12:10 -0700, Tom Tromey wrote:
> This is ok.
Retested and committed to trunk and 4.1 branch.
> I'd like to make sure we can eventually get rid of this override
> though. At the very least we need to update the existing PR to
> account for this...
I updated the bug report to mention the override files. And the commit
message references the bug number.
Cheers,
Mark
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-11-26 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 0:04 Mark Wielaard
2005-11-20 19:10 ` Mark Wielaard
2005-11-24 16:19 ` Mark Wielaard
2005-11-25 19:22 ` Tom Tromey
2005-11-26 0:53 ` Mark Wielaard [this message]
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=1132966208.5509.140.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=java-patches@gcc.gnu.org \
--cc=tromey@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).