From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Capture many-headers.exp progress and output in gdb.log
Date: Sun, 09 Feb 2020 12:17:00 -0000 [thread overview]
Message-ID: <54dbf617-53ed-d595-5c17-8319541cf308@simark.ca> (raw)
In-Reply-To: <e7448004-8e54-dd2b-c72e-a23f0df4e373@suse.de>
On 2020-02-09 7:07 a.m., Tom de Vries wrote:
>> This leaves a stray OUTPUT file in the build/gdb/testsuite directory.
>
> Removed in updated version.
>
>> I am fine
>> with the technique used, but maybe just create some file using standard_output_file?
>
> Done.
>
> Thanks,
> - Tom
>
>
Thanks, that LGTM.
Simon
prev parent reply other threads:[~2020-02-09 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 8:53 Tom de Vries
2020-02-08 16:16 ` Simon Marchi
2020-02-09 12:07 ` Tom de Vries
2020-02-09 12:17 ` Simon Marchi [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=54dbf617-53ed-d595-5c17-8319541cf308@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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