Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] [gdb/testsuite] Use try instead of catch
Date: Fri, 23 Oct 2026 06:26:30 -0700	[thread overview]
Message-ID: <045acbd8-adcf-4cd0-b129-50dbcefa72da@redhat.com> (raw)
In-Reply-To: <71d772a5-5ff8-4363-9ca1-8a1df30a11c1@suse.de>

On 10/23/26 4:11 AM, Tom de Vries wrote:
> On 10/22/26 4:22 PM, Keith Seitz wrote:
> thanks for the review.
> 
> The Linaro CI did run into this problem, so I've already addressed this 
> in a v2.
Oh, my! My inbox is such a mess, I didn't even see your v2. That updated
bit addresses everything.

I'm very sorry about the confusion/old revision review.

Keith


      reply	other threads:[~2026-10-23 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 14:01 [PATCH 0/2] " Tom de Vries
2026-09-25 14:01 ` [PATCH 1/2] [gdb/testsuite] Simplify core_find Tom de Vries
2026-09-25 14:01 ` [PATCH 2/2] [gdb/testsuite] Use try instead of catch Tom de Vries
2026-10-22 14:22   ` Keith Seitz
2026-10-23 11:11     ` Tom de Vries
2026-10-23 13:26       ` Keith Seitz [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=045acbd8-adcf-4cd0-b129-50dbcefa72da@redhat.com \
    --to=keiths@redhat.com \
    --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