From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/2] Add Rust support to source highlighting
Date: Mon, 19 Aug 2019 16:19:00 -0000 [thread overview]
Message-ID: <87imqtqga7.fsf@tromey.com> (raw)
In-Reply-To: <20190727155155.32417-1-tom@tromey.com> (Tom Tromey's message of "Sat, 27 Jul 2019 09:51:53 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> This is v2 of the patch to add Rust support to source highlighting.
Tom> This version addresses the --static-libstdc++ problem that was found
Tom> with the previous patch, using the approach suggested by Pedro.
Tom> Let me know what you think. If this seems ok, my plan is to send the
Tom> top-level configury patch to gcc-patches for approval, and only then
Tom> check everything in. This plan avoids any problem if the gcc
Tom> maintainers request a different option name.
I've checked in the gcc patch, and I've updated the gdb patch to account
for other recent changes to source-cache.c. I am going to check this in
now.
Tom
next prev parent reply other threads:[~2019-08-19 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 15:52 Tom Tromey
2019-07-27 15:52 ` [PATCH v2 2/2] " Tom Tromey
2019-09-04 17:22 ` Tom de Vries
2019-09-10 15:56 ` Tom Tromey
2019-09-12 19:20 ` Tom de Vries
2019-09-17 18:24 ` Tom Tromey
2019-09-18 22:16 ` Tom de Vries
2019-09-19 12:54 ` Tom Tromey
2019-09-19 16:18 ` [PATCH][gdb] Catch exception when constructing the highlighter Tom de Vries
2019-07-27 15:52 ` [PATCH v2 1/2] Add --with-static-standard-libraries to the top level Tom Tromey
2019-08-19 16:19 ` Tom Tromey [this message]
2019-08-19 18:29 ` [PATCH v2 0/2] Add Rust support to source highlighting Pedro Alves
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=87imqtqga7.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