From: Joseph Myers <joseph@codesourcery.com>
To: Costas Argyris <costas.argyris@gmail.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] gcc-ar: Handle response files properly [PR77576]
Date: Fri, 28 Jul 2023 21:11:53 +0000 [thread overview]
Message-ID: <daacecc-ca81-1ba3-4ab9-5a18468cbd32@codesourcery.com> (raw)
In-Reply-To: <CAHyHGCnC7VmVVwekN0TipNA8UXcthGHcggYTo_k=_xxaikDc7Q@mail.gmail.com>
This patch is OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-07-28 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 21:45 Costas Argyris
2023-07-03 11:07 ` Costas Argyris
2023-07-07 10:33 ` Costas Argyris
2023-07-07 12:00 ` Costas Argyris
2023-07-14 8:05 ` Costas Argyris
2023-07-28 11:59 ` Costas Argyris
2023-07-28 21:11 ` Joseph Myers [this message]
2023-07-31 16:58 ` Jeff Law
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=daacecc-ca81-1ba3-4ab9-5a18468cbd32@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=costas.argyris@gmail.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).