unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: naohirot--- via Libc-alpha <libc-alpha@sourceware.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: 'GNU C Library' <libc-alpha@sourceware.org>
Subject: RE: [PATCH v3 1/5] AArch64: Improve A64FX memset
Date: Tue, 3 Aug 2021 02:56:35 +0000	[thread overview]
Message-ID: <TYAPR01MB60255BEFDB338F53688CD4B4DFF09@TYAPR01MB6025.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <VE1PR08MB5599AC44FC079BAA03DE9C5383EF9@VE1PR08MB5599.eurprd08.prod.outlook.com>

Hi Wilco,

> > Would you update the commit title so as not to be the same among 5
> > patches?
> > Because we need to ask distro to backport these patches.
> > If all commit titles are the same, it will increase the room to happen
> > confusion and mistake.
> >
> > How about "AArch64: Improve A64FX memset for less than 512B" ?
> 
> Generally the commit title in a patch series would include the series number,
> however it's also easy to add something to the title as suggested. As for
> backporting, one uses the hash of the patch in the cherry-pick rather than
> the title, so once you have the right hashes, there should be no possibility
> of confusion.

Thank you for considering it.
If communication made among engineers, I think the series number is
enough.
But we don't know if people in the middle of engineer to engineer
communication knows git :-)

Thanks.
Naohiro



      parent reply	other threads:[~2021-08-03  2:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 15:59 [PATCH v3 1/5] AArch64: Improve A64FX memset Wilco Dijkstra via Libc-alpha
2021-07-28  8:10 ` naohirot--- via Libc-alpha
2021-08-02 13:53   ` naohirot--- via Libc-alpha
2021-08-02 14:38     ` Wilco Dijkstra via Libc-alpha
2021-08-02 14:50       ` Szabolcs Nagy via Libc-alpha
2021-08-03  2:57         ` naohirot--- via Libc-alpha
2021-08-03  8:01           ` Szabolcs Nagy via Libc-alpha
2021-09-24  7:56             ` naohirot--- via Libc-alpha
2021-08-03  2:56       ` naohirot--- via Libc-alpha [this message]

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=TYAPR01MB60255BEFDB338F53688CD4B4DFF09@TYAPR01MB6025.jpnprd01.prod.outlook.com \
    --to=libc-alpha@sourceware.org \
    --cc=Wilco.Dijkstra@arm.com \
    --cc=naohirot@fujitsu.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).