From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Delayed physname computation
Date: Fri, 23 Apr 2010 23:04:00 -0000 [thread overview]
Message-ID: <m3633hwz31.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100421063824.GA11777@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed, 21 Apr 2010 08:38:24 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> testsuite/
Jan> 2010-04-21 Keith Seitz <keiths@redhat.com>
Jan> Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> * gdb.dwarf2/pr11465.exp: New test.
Jan> * gdb.dwarf2/pr11465.S: New file.
For the record, this is ok when Keith's patch is ok.
I think the two should be merged into a single commit.
Tom
next prev parent reply other threads:[~2010-04-23 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 20:23 Keith Seitz
2010-04-21 6:38 ` Jan Kratochvil
2010-04-23 23:04 ` Tom Tromey [this message]
2010-04-23 23:03 ` Tom Tromey
2010-04-23 23:34 ` Keith Seitz
2010-04-26 18:38 ` Tom Tromey
2010-05-11 21:18 ` Keith Seitz
2010-06-04 22:37 ` Tom Tromey
2010-04-25 10:33 ` Jan Kratochvil
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=m3633hwz31.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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).