From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] comdat types
Date: Wed, 15 Jul 2009 19:28:00 -0000 [thread overview]
Message-ID: <m3prc1hj0h.fsf@fleche.redhat.com> (raw)
In-Reply-To: <e394668d0907141629i53b6b9d2o49e0ca7e43ed58f5@mail.gmail.com> (Doug Evans's message of "Tue\, 14 Jul 2009 16\:29\:34 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> How about this?
Doug> It addresses the issues raised here:
Doug> http://sourceware.org/ml/gdb-patches/2009-06/msg00689.html
Now that you are a global maintainer (congratulations!) I think you
ought to self-approve it. There has been plenty of time for comments.
BTW, what is the status of the GCC patch?
Tom
next prev parent reply other threads:[~2009-07-15 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 0:04 Doug Evans
2009-06-25 19:47 ` Tom Tromey
2009-06-25 20:28 ` Doug Evans
2009-06-25 20:49 ` Tom Tromey
2009-07-15 1:13 ` Doug Evans
2009-07-15 19:28 ` Tom Tromey [this message]
2009-07-16 1:25 ` Doug Evans
2009-07-21 0:10 ` Cary Coutant
2009-06-26 1:33 ` Daniel Jacobowitz
2009-06-26 0:01 ` Cary Coutant
2009-06-26 0:54 ` Doug Evans
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=m3prc1hj0h.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@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