From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/testsuite] Fix gdb.multi/multi-term-settings.exp
Date: Wed, 29 Sep 2021 12:18:34 +0100 [thread overview]
Message-ID: <bfc72903-0850-91ce-9d0d-3a55f25217a1@palves.net> (raw)
In-Reply-To: <faf86428-866b-9a3e-5fd2-668162a4e538@suse.de>
On 2021-09-28 11:42 p.m., Tom de Vries wrote:
> On 9/28/21 8:14 PM, Pedro Alves wrote:
>> Hmm, think rang a bell. I had posted a patch for this a few months back:
>>
>> https://sourceware.org/pipermail/gdb-patches/2021-June/179503.html
>>
>> The idea is the same, but my version is more complete, IMHO.
>>
>> Sorry I didn't think of splitting that one out of the series at the time, this
>> could have been fixed all this time. :-/
>>
>
> Np. I applied the patch locally and it works for me.
>
> Anything preventing this from going in now?
Not really. Since you have it handy, can you push it?
next prev parent reply other threads:[~2021-09-29 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 17:57 Tom de Vries via Gdb-patches
2021-09-28 18:14 ` Pedro Alves
2021-09-28 22:42 ` Tom de Vries via Gdb-patches
2021-09-29 11:18 ` Pedro Alves [this message]
2021-09-29 13:56 ` Tom de Vries via Gdb-patches
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=bfc72903-0850-91ce-9d0d-3a55f25217a1@palves.net \
--to=pedro@palves.net \
--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