From: Richard Biener <richard.guenther@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: YunQiang Su <wzssyqa@gmail.com>,
Collin Funk <collin.funk1@gmail.com>,
gcc-patches@gcc.gnu.org, cohenarthur@gcc.gnu.org
Subject: Re: [PATCH] build: Fix missing variable quotes
Date: Tue, 18 Jun 2024 12:33:30 +0200 [thread overview]
Message-ID: <CAFiYyc1eVGyBSR0irpzY9KHD7cjK5AgzF2jBPbE9dZq1TUtViw@mail.gmail.com> (raw)
In-Reply-To: <87frta3b0u.fsf@gentoo.org>
On Tue, Jun 18, 2024 at 10:35 AM Sam James <sam@gentoo.org> wrote:
>
> YunQiang Su <wzssyqa@gmail.com> writes:
>
> > OK for trunk?
>
> It looks good to me, but I can't approve. (I'd dare say it's obvious,
> even.)
>
> Richard, any chance you could give it a quick ack?
OK
next prev parent reply other threads:[~2024-06-18 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 0:53 Collin Funk
2024-06-14 1:01 ` Sam James
2024-06-14 9:01 ` YunQiang Su
2024-06-18 8:13 ` YunQiang Su
2024-06-18 8:33 ` Sam James
2024-06-18 10:33 ` Richard Biener [this message]
2024-06-14 10:46 ` Arthur Cohen
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=CAFiYyc1eVGyBSR0irpzY9KHD7cjK5AgzF2jBPbE9dZq1TUtViw@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=cohenarthur@gcc.gnu.org \
--cc=collin.funk1@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sam@gentoo.org \
--cc=wzssyqa@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).