From: Janis Johnson <janisjo@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] let gdb.base/reread.exp handle multiple binary files
Date: Thu, 05 May 2011 16:32:00 -0000 [thread overview]
Message-ID: <4DC2D106.3060806@codesourcery.com> (raw)
In-Reply-To: <201105041855.32567.pedro@codesourcery.com>
On 05/04/2011 10:55 AM, Pedro Alves wrote:
> On Wednesday 04 May 2011 17:47:45, Janis Johnson wrote:
>> 20110-5-04 Janis Johnson <janisjo@codesourcery.com>
>
> Typo.
>
>>
>> * lib/gdb.exp (exec_target_file, exec_symbol_file,
>> gdb_rename_execfile, gdb_touch_execfile): New.
>> * gdb.base/reread.exp: Use new procs to handle multiple
>> exec files.
>
> Okay.
Thanks, I got set up with write access and checked it in.
Janis
next prev parent reply other threads:[~2011-05-05 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 16:47 Janis Johnson
2011-05-04 17:55 ` Pedro Alves
2011-05-05 16:32 ` Janis Johnson [this message]
2011-05-07 6:05 ` Regression: " Jan Kratochvil
2011-05-08 9:08 ` [patch] Regression: " Jan Kratochvil
2011-05-11 7:08 ` [patch#2] " Jan Kratochvil
2011-05-11 9:03 ` Pedro Alves
2011-05-11 9:12 ` 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=4DC2D106.3060806@codesourcery.com \
--to=janisjo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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