public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "free_software at fastmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/28437] Internal error with `fs status` followed by `fs next`
Date: Wed, 15 Feb 2023 09:40:01 +0000 [thread overview]
Message-ID: <bug-28437-4717-mLKBkEM9VP@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28437-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28437
Julien <free_software at fastmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|VERIFIED |RESOLVED
--- Comment #5 from Julien <free_software at fastmail dot com> ---
Apologies, my previous comment might have been too hasty. I just checked and
noticed the referenced commit wasn't included in 12.1.
I'll come back to this once 13.1 is up and running on my computer. Moving this
back to RESOLVED FIXED - thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-15 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 0:37 [Bug tui/28437] New: `fs status` followed by `fs next` fails to switch focus on Mac sourceware at fastmail dot com
2021-10-09 1:45 ` [Bug tui/28437] Internal error with `fs status` followed by `fs next` simark at simark dot ca
2021-10-09 1:46 ` simark at simark dot ca
2021-10-09 1:53 ` sourceware at fastmail dot com
2023-02-12 19:57 ` tromey at sourceware dot org
2023-02-15 9:27 ` free_software at fastmail dot com
2023-02-15 9:40 ` free_software at fastmail dot com [this message]
2023-02-15 21:42 ` tromey at sourceware dot org
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=bug-28437-4717-mLKBkEM9VP@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).