From: LRN <lrn1986@gmail.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Apply substitute-path to relative filenames as well
Date: Wed, 13 Mar 2019 12:47:00 -0000 [thread overview]
Message-ID: <5415b22f-c46c-8dbf-4481-98be267e25bb@gmail.com> (raw)
In-Reply-To: <871s3lq8fy.fsf@tromey.com>
[-- Attachment #1.1: Type: text/plain, Size: 182 bytes --]
On 06.03.2019 1:10, Tom Tromey wrote:
> Thank you for the patch.
>
Hey, it's been a week. Do i need to do something to move this along? (Please,
don't say "test case" :( )
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-13 12:47 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 [this message]
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
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=5415b22f-c46c-8dbf-4481-98be267e25bb@gmail.com \
--to=lrn1986@gmail.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