From: Tom Tromey <tromey@redhat.com>
To: Paul Hilfinger <Hilfinger@cs.berkeley.edu>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com
Subject: Re: [RFA] Refactor 'maint time' command statistics.
Date: Fri, 25 Jun 2010 20:43:00 -0000 [thread overview]
Message-ID: <m3iq564zee.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1277497082-4990-1-git-send-email-Hilfinger@cs.berkeley.edu> (Paul Hilfinger's message of "Fri, 25 Jun 2010 13:18:02 -0700")
>>>>> "Paul" == Paul Hilfinger <Hilfinger@cs.berkeley.edu> writes:
Paul> Oops. My mistake. I left off a necessary change in the
Paul> gdb.gdb/selftest.exp test to compensate for modifications to
Paul> captured_main. Here is the revision, with Tom's modifications.
Paul> If there is no further objection, I will commit in a day or so.
It is fine with me. Thanks.
Tom
next prev parent reply other threads:[~2010-06-25 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 8:23 Paul Hilfinger
2010-06-24 16:21 ` Tom Tromey
2010-06-25 20:19 ` Paul Hilfinger
2010-06-25 20:43 ` Tom Tromey [this message]
2010-06-26 7:19 ` [commit] " Paul Hilfinger
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=m3iq564zee.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Hilfinger@cs.berkeley.edu \
--cc=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).