From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Fix regexp in gdb.ada/mi_var_access.exp
Date: Tue, 14 Jun 2022 11:10:12 +0200 [thread overview]
Message-ID: <38e9a001-f832-0ee9-56d4-f13e5f9cbe4f@suse.de> (raw)
In-Reply-To: <04e6e253-22c2-951b-c9ca-ed85f37836ac@suse.de>
On 6/10/22 09:09, Tom de Vries wrote:
> On 6/10/22 09:04, Tom de Vries via Gdb-patches wrote:
>> Bug:https://sourceware.org/bugzilla/show_bug.cgi?id=27027
>
> Hmm, I also submitted this yesterday, but missed that today because I
> included the wrong Bug line, this should be:
> ...
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28464
> ...
Committed.
Thanks,
- Tom
prev parent reply other threads:[~2022-06-14 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 7:04 [PATCH][gdb/testsuite] " Tom de Vries
2022-06-10 7:09 ` Tom de Vries
2022-06-14 9:10 ` 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:
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=38e9a001-f832-0ee9-56d4-f13e5f9cbe4f@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).