From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: caiyinyu <caiyinyu@loongson.cn>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH] Update miscellaneous files from upstream sources
Date: Mon, 11 Jul 2022 16:07:24 +0200 [thread overview]
Message-ID: <87h73n3fqb.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220711130431.25145-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Mon, 11 Jul 2022 10:04:31 -0300")
* Adhemerval Zanella via Libc-alpha:
> This patch updates various miscellaneous files from their upstream
> sources (version 2022-05-25).
>
> It is required for loongarch support.
>
> Checked on aarch64-linux-gnu.
Files match latest upstream version. Commit subject could say
“Update scripts/config.* files from upstream GNU config version”
or something like that, given those are the only two files being
updated.
Thanks,
Florian
next prev parent reply other threads:[~2022-07-11 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:04 Adhemerval Zanella
2022-07-11 14:07 ` Florian Weimer [this message]
2022-07-11 14:58 ` Adhemerval Zanella
2022-07-11 15:11 ` Carlos O'Donell
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=87h73n3fqb.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=libc-alpha@sourceware.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).