From: Hongyu Wang <wwwhhhyyy333@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: Jonathan Wakely <jwakely@redhat.com>,
Hongyu Wang <hongyu.wang@intel.com>,
gcc-patches@gcc.gnu.org, hongtao.liu@intel.com,
ubizjak@gmail.com
Subject: Re: [PATCH] doc: Reword the description of -mrelax-cmpxchg-loop [PR 107676]
Date: Wed, 16 Nov 2022 16:29:53 +0800 [thread overview]
Message-ID: <CA+OydWk9qP6wsF3zaqeJLqaBNJ+G7_mH_Q2RyP8B4uRW8ESCHQ@mail.gmail.com> (raw)
In-Reply-To: <36b75ee4-5f97-16ab-8d9d-a060e996b5da@ispras.ru>
> Please use 'git commit --author' to indicate authorship of the patch
> (or simply let me push it once approved).
Yes, just change the author and push it.
Thanks for your help!
next prev parent reply other threads:[~2022-11-16 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 3:35 Hongyu Wang
2022-11-15 10:53 ` Jonathan Wakely
2022-11-15 13:28 ` Alexander Monakov
2022-11-15 13:44 ` Jonathan Wakely
2022-11-15 13:59 ` Alexander Monakov
2022-11-16 5:15 ` Hongyu Wang
2022-11-16 7:51 ` Alexander Monakov
2022-11-16 8:29 ` Hongyu Wang [this message]
2022-11-16 10:51 ` Jonathan Wakely
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=CA+OydWk9qP6wsF3zaqeJLqaBNJ+G7_mH_Q2RyP8B4uRW8ESCHQ@mail.gmail.com \
--to=wwwhhhyyy333@gmail.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=hongyu.wang@intel.com \
--cc=jwakely@redhat.com \
--cc=ubizjak@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).