From: Joseph Myers <joseph@codesourcery.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Martin Liska <marxin@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: [gcc r12-6020] Fixed typo
Date: Thu, 16 Dec 2021 18:43:24 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2112161841500.1715763@digraph.polyomino.org.uk> (raw)
In-Reply-To: <d693e665-902c-100e-74f7-a8fcd05b92d8@suse.cz>
On Thu, 16 Dec 2021, Martin Liška wrote:
> Hello.
>
> Oh, sorry, it was me and I forgot to send the patch to the mailing list.
> I've basically taken it as: https://github.com/gcc-mirror/gcc/pull/57.
>
> Should I revert the change?
Updating both config.sub and config.guess to the latest config.git
versions (2021-10-27 and 2021-11-30) is probably the right thing to do
now.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-12-16 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211216165513.EBA843858D28@sourceware.org>
2021-12-16 18:32 ` Joseph Myers
2021-12-16 18:38 ` Martin Liška
2021-12-16 18:43 ` Joseph Myers [this message]
2021-12-17 9:53 ` Martin Liška
2021-12-20 18:19 ` Rainer Orth
2021-12-21 8:13 ` Martin Liška
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=alpine.DEB.2.22.394.2112161841500.1715763@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marxin@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).