From: Serge Belyshev <belyshev@depni.sinp.msu.ru>
To: gcc-patches@gcc.gnu.org
Subject: PING^3: [PATCH] Add --enable-first-stage-cross configure option
Date: Mon, 17 Jan 2022 00:13:02 +0300 [thread overview]
Message-ID: <87k0ezo04h.fsf_-_@depni.sinp.msu.ru> (raw)
In-Reply-To: <87tuec8usd.fsf_-_@depni.sinp.msu.ru> (Serge Belyshev's message of "Mon, 10 Jan 2022 00:26:58 +0300")
Final ping before stage3 ends:
[PATCH] Add --enable-first-stage-cross configure option
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575318.html
next prev parent reply other threads:[~2022-01-16 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 13:39 Serge Belyshev
2021-09-06 13:13 ` Ping: " Serge Belyshev
2022-01-09 21:26 ` PING^2: " Serge Belyshev
2022-01-10 15:10 ` Jonathan Wakely
2022-01-16 21:13 ` Serge Belyshev [this message]
2022-07-10 3:13 ` Jeff Law
2022-07-13 9:35 ` Serge Belyshev
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=87k0ezo04h.fsf_-_@depni.sinp.msu.ru \
--to=belyshev@depni.sinp.msu.ru \
--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).