public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Palmer Dabbelt <palmer@dabbelt.com>
Cc: rdapp.gcc@gmail.com, gcc-patches@gcc.gnu.org,
	juzhe.zhong@rivai.ai, collison@rivosinc.com
Subject: Re: [PATCH] riscv: Add autovectorization tests for binary integer
Date: Wed, 10 May 2023 21:30:45 -0600	[thread overview]
Message-ID: <b178224d-fb7a-73c0-3729-5ae6547b3c84@gmail.com> (raw)
In-Reply-To: <CA+yXCZD8X+HB2xDEH=7N3j+G0oe2Ys3_COws0tekNZ7Dkk35Mg@mail.gmail.com>



On 5/10/23 20:26, Kito Cheng wrote:
> Don't forgot to add Michael to co-author, you can added by following line:
> 
> Co-authored-by: Michael Collison <collison@rivosinc.com>
> 
> And GCC's changelog generating script will recognize that and generate
> the right thing for that :)
Thanks for pointing that out.  I was looking for something similar to 
--author, but didn't find anything (of course).  I didn't realize it was 
actually handled by looking for tags in the commit message.

Jeff

  reply	other threads:[~2023-05-11  3:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 15:24 Robin Dapp
2023-05-10 19:19 ` Palmer Dabbelt
2023-05-11  2:26   ` Kito Cheng
2023-05-11  3:30     ` Jeff Law [this message]
2023-05-11 10:27     ` [PATCH v2] RISC-V: Add autovectorization tests for binary integer, operations Robin Dapp
2023-05-11 10:35       ` juzhe.zhong
2023-05-11 11:09         ` Kito Cheng
2023-05-11  2:32 ` [PATCH] riscv: Add autovectorization tests for binary integer juzhe.zhong
2023-05-15  9:10 ` Andreas Schwab
2023-05-15  9:15   ` juzhe.zhong
2023-05-16  4:19     ` Jeff Law

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=b178224d-fb7a-73c0-3729-5ae6547b3c84@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=collison@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=rdapp.gcc@gmail.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).