From: naohirot--- via Libc-alpha <libc-alpha@sourceware.org>
To: 'Florian Weimer' <fweimer@redhat.com>,
"'libc-alpha@sourceware.org'" <libc-alpha@sourceware.org>
Cc: 'Szabolcs Nagy' <szabolcs.nagy@arm.com>,
'Wilco Dijkstra' <Wilco.Dijkstra@arm.com>
Subject: [PATCH] AArch64: Update A64FX memset not to degrade at 16KB
Date: Mon, 6 Sep 2021 08:44:27 +0000 [thread overview]
Message-ID: <TYAPR01MB60256AD2A873A0E1A3662A22DFD29@TYAPR01MB6025.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYAPR01MB602525FB59480A6CEF989F9CDFD29@TYAPR01MB6025.jpnprd01.prod.outlook.com>
Hi Florian, Szabolcs, and All maintainers,
> From: Florian Weimer <fweimer@redhat.com>
> Sent: Monday, September 6, 2021 3:18 PM
> * naohirot:
>
> > I noticed that my email address is not right in the commit log,
> > would you please fix it to <naohirot@fujitsu.com>?
> >
> > commit 23777232c23f80809613bdfa329f63aadf992922
> > Author: Naohiro Tamura via Libc-alpha <libc-alpha@sourceware.org>
> > Date: Fri Aug 27 05:03:04 2021 +0000
>
> It's probably too late to do this now because it would mean rewriting
> history.
Yes, I know that it's impossible update only email address in the commit log.
Currently there are two commits after the patch, so rewriting history involves
only three records.
If rewriting history is not acceptable, I prefer to revert and recommit.
"Author: " line in the commit log is the identity for each contributor.
And it's related to the " Update to glibc copyright assignment policy" discussion.
So I'd like to hear other maintainer's opinion.
Thanks.
Naohiro
next prev parent reply other threads:[~2021-09-06 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 5:03 [PATCH] AArch64: Update A64FX memset not to degrade at 16KB Naohiro Tamura via Libc-alpha
2021-09-03 15:01 ` Szabolcs Nagy via Libc-alpha
2021-09-05 23:51 ` naohirot--- via Libc-alpha
2021-09-06 0:16 ` naohirot--- via Libc-alpha
2021-09-06 6:17 ` Florian Weimer via Libc-alpha
[not found] ` <TYAPR01MB602525FB59480A6CEF989F9CDFD29@TYAPR01MB6025.jpnprd01.prod.outlook.com>
2021-09-06 8:44 ` naohirot--- via Libc-alpha [this message]
2021-09-06 10:20 ` 'Szabolcs Nagy' via Libc-alpha
2021-09-06 11:56 ` naohirot--- via Libc-alpha
2021-09-06 15:54 ` Joseph Myers
2021-09-16 11:53 ` Florian Weimer via Libc-alpha
2021-09-17 0:49 ` naohirot--- via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TYAPR01MB60256AD2A873A0E1A3662A22DFD29@TYAPR01MB6025.jpnprd01.prod.outlook.com \
--to=libc-alpha@sourceware.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=fweimer@redhat.com \
--cc=naohirot@fujitsu.com \
--cc=szabolcs.nagy@arm.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).