From: Jeff Law <jeffreyalaw@gmail.com>
To: Patrick O'Neill <patrick@rivosinc.com>, gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com, palmer@rivosinc.com, rep.dot.nop@gmail.com
Subject: Re: [PATCH] RISC-V: Name newly added flags in changelog
Date: Tue, 2 May 2023 09:50:01 -0600 [thread overview]
Message-ID: <60a6955f-d5a9-db7d-c9e5-a6658ccb840e@gmail.com> (raw)
In-Reply-To: <20230501161037.614414-1-patrick@rivosinc.com>
On 5/1/23 10:10, Patrick O'Neill wrote:
> This patch fixes the changelog to explicitly name the added command line
> flags introduced in this patch:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616807.html
>
> 2023-05-01 Patrick O'Neill <patrick@rivosinc.com>
>
> gcc/ChangeLog:
>
> * ChangeLog: Name the flags added by the patch in the changelog.
OK. You *might* not actually need a ChangeLog entry for this. The
hooks *might* have a special case for fixing up the ChangeLog entries.
jeff
next prev parent reply other threads:[~2023-05-02 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 16:10 Patrick O'Neill
2023-05-02 15:50 ` Jeff Law [this message]
2023-05-02 16:24 ` Patrick O'Neill
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=60a6955f-d5a9-db7d-c9e5-a6658ccb840e@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=palmer@rivosinc.com \
--cc=patrick@rivosinc.com \
--cc=rep.dot.nop@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).