From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] [gdb/cli] Skip string copy in source_cache::ensure
Date: Fri, 13 Oct 2023 14:21:35 +0200 [thread overview]
Message-ID: <0d59e5b0-1f10-4b70-bf0a-54dbe4505d83@suse.de> (raw)
In-Reply-To: <20231012144707.13931-1-tdevries@suse.de>
I've submitted a v2 series here (
https://sourceware.org/pipermail/gdb-patches/2023-October/203199.html ).
Thanks,
- Tom
prev parent reply other threads:[~2023-10-13 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 14:47 Tom de Vries
2023-10-12 14:47 ` [PATCH 2/4] [gdb/cli] Factor out try_source_highlight Tom de Vries
2023-10-12 14:47 ` [PATCH 3/4] [gdb/cli] Keep track of styling failures in source_cache Tom de Vries
2023-10-12 14:47 ` [PATCH 4/4] [gdb/cli] Allow source highlighting to be interrupted Tom de Vries
2023-10-13 12:21 ` 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=0d59e5b0-1f10-4b70-bf0a-54dbe4505d83@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).