From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: LRN <lrn1986@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Apply substitute-path to relative filenames as well
Date: Thu, 06 Jun 2019 18:01:00 -0000 [thread overview]
Message-ID: <87zhmu8ug3.fsf@tromey.com> (raw)
In-Reply-To: <87a7hdcsl8.fsf@tromey.com> (Tom Tromey's message of "Fri, 29 Mar 2019 14:51:15 -0600")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>>>>> "LRN" == LRN <lrn1986@gmail.com> writes:
LRN> Anyway, that still sounds an order of magnitude more complicated that
LRN> subst.exp, so i would rather not try to implement all that using completely
LRN> unfamiliar testing framework that i do not have.
Tom> Alright, I will see if I can write one.
LRN> I did address it. The first follow-up[0] message had the new version of the
LRN> patch attached, with the nit fixed.
Tom> Thanks, I must have missed that.
I'm checking this in. I finally looked, and writing a test did seem
like a pain.
Tom
prev parent reply other threads:[~2019-06-06 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 12:52 LRN
2019-03-05 22:24 ` Tom Tromey
2019-03-06 10:06 ` LRN
2019-03-13 12:47 ` LRN
2019-03-20 10:24 ` LRN
2019-03-27 21:36 ` Tom Tromey
2019-03-27 22:59 ` LRN
2019-03-29 20:51 ` Tom Tromey
2019-06-06 18:01 ` Tom Tromey [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=87zhmu8ug3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=lrn1986@gmail.com \
/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