public inbox for
 help / color / mirror / Atom feed
From: Tom de Vries <>
To: Luis Machado <>,
Subject: Re: [PATCH] [gdb/testsuite] Fix linespec ambiguity in gdb.base/longjmp.exp
Date: Fri, 10 Feb 2023 16:00:34 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2/10/23 15:58, Luis Machado wrote:
> Thanks Tom. I gave this a try and it fixes the FAIL's I was seeing.
> Reviewed-By: Luis Machado <>
> Tested-By: Luis Machado <>

Thanks for confirming.

Unfortunately, I was once more too trigger-happy, so the commit is 
missing your tested-by tag.

- Tom

      reply	other threads:[~2023-02-10 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 10:57 Tom de Vries
2023-02-10 14:36 ` Tom Tromey
2023-02-10 14:58 ` Luis Machado
2023-02-10 15:00   ` Tom de Vries [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).