From: Lancelot SIX <Lancelot.Six@amd.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, tdevries@suse.de
Subject: Re: [PATCH] Revert "gdb/compile: Use std::filesystem::remove_all in cleanup"
Date: Wed, 3 Apr 2024 16:35:20 +0100 [thread overview]
Message-ID: <0eaaa59e-cf11-4768-bdd4-3546e4c6e32d@amd.com> (raw)
In-Reply-To: <87a5ma8pav.fsf@tromey.com>
>
> Thanks. Could you put the 'Bug:' tag into this so it's recorded in
> bugzilla?
>
> Sorry to say it but this is ok. I appreciate your quick turnaround on
> it.
>
> Approved-By: Tom Tromey <tom@tromey.com>
>
> Tom
I have added the Bug tag and pushed to master. This should fix the
issues for builders with older toolchains.
Thanks,
Lancelot.
prev parent reply other threads:[~2024-04-03 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 14:44 Lancelot SIX
2024-04-03 14:59 ` Tom Tromey
2024-04-03 15:35 ` Lancelot SIX [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=0eaaa59e-cf11-4768-bdd4-3546e4c6e32d@amd.com \
--to=lancelot.six@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).