From: Tom Tromey <tromey@adacore.com>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Move include block to pathstuff.h (no-tn-check)
Date: Tue, 10 Nov 2020 13:11:51 -0700 [thread overview]
Message-ID: <87mtzpezug.fsf@tromey.com> (raw)
In-Reply-To: <a85a6b43-2ab6-6e4f-62e4-1c7c07640c54@simark.ca> (Simon Marchi's message of "Tue, 10 Nov 2020 12:14:43 -0500")
>> gdbsupport/ChangeLog
>> 2020-11-10 Tom Tromey <tromey@adacore.com>
>>
>> * pathstuff.h: Move include block here...
>> * pathstuff.cc: ... from here.
Simon> Does this fix this bug?
Yep, thanks.
Simon> https://sourceware.org/bugzilla/show_bug.cgi?id=26848
Simon> If so, you could add a PR reference and close it. The patch LGTM, since
Simon> we reached the same conclusion.
Will do, thank you.
Tom
prev parent reply other threads:[~2020-11-10 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 16:57 Tom Tromey
2020-11-10 17:14 ` Simon Marchi
2020-11-10 20:11 ` 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=87mtzpezug.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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