From: Tom Tromey <tom@tromey.com>
To: Keith Seitz via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: C++ template completion support v3
Date: Fri, 18 Feb 2022 13:34:40 -0700 [thread overview]
Message-ID: <87fsofrk0v.fsf@tromey.com> (raw)
In-Reply-To: <20211209191750.2601228-1-keiths@redhat.com> (Keith Seitz via Gdb-patches's message of "Thu, 9 Dec 2021 11:17:47 -0800")
>>>>> "Keith" == Keith Seitz via Gdb-patches <gdb-patches@sourceware.org> writes:
Keith> I would like to resurrect this patch series (after a very long hiatus).
Keith> There are minimal changes to the original series, last posted here:
Keith> https://sourceware.org/pipermail/gdb-patches/2020-April/167780.html
Keith> During that last series, Tom (Tromey) gave it the LGTM, but there was
Keith> a request to add unittests for strncmp_iw_with_mode. This new series
Keith> accommodates that request.
Keith> The second patch from the original submission ("Remove hard-coded
Keith> line number from templates.exp") is no longer necessary,
Keith> having been fixed by Andrew Burgess in November.
Sorry about the delay on this.
I think this is OK.
thanks,
Tom
next prev parent reply other threads:[~2022-02-18 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 19:17 Keith Seitz
2021-12-09 19:17 ` [PATCH v3 1/3] Move find_toplevel_char to cp-support.[ch] Keith Seitz
2021-12-09 19:17 ` [PATCH v3 2/3] Unit tests for strncmp_iw_with_mode Keith Seitz
2021-12-09 19:17 ` [PATCH v3 3/3] Support template lookups in strncmp_iw_with_mode Keith Seitz
2021-12-09 19:40 ` Eli Zaretskii
2021-12-10 20:54 ` Keith Seitz
2022-02-18 20:34 ` Tom Tromey [this message]
2022-02-24 17:47 ` C++ template completion support v3 Keith Seitz
2022-02-24 21:33 ` Tom Tromey
2022-02-25 0:49 ` Keith Seitz
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=87fsofrk0v.fsf@tromey.com \
--to=tom@tromey.com \
--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).