From: Jason Merrill <jason@redhat.com>
To: nick huang <nickhuang99@hotmail.com>,
Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++: Suppress error when cv-qualified reference is introduced by typedef [PR101783]
Date: Fri, 1 Oct 2021 09:29:05 -0400 [thread overview]
Message-ID: <7ff72053-60e7-3c9b-3737-458ec40f1f77@redhat.com> (raw)
In-Reply-To: <DM5PR0501MB37332F0CFBA3F98E949FB9C8B5AA9@DM5PR0501MB3733.namprd05.prod.outlook.com>
On 9/30/21 14:24, nick huang wrote:
>>> You may need to run contrib/gcc-git-customization.sh to get the git
>>> gcc-verify command.
> I re-setup and can use git gcc-verify. Now I can see it rejects because I forgot to add a
> description of modified file. Now that it passes gcc-verify and I attach the changelog
> as attachment.
>
> Thank you again for your patient explanation and help!
You're welcome, thanks for your patience as well! Unfortunately, git
gcc-verify still fails with this version:
> ERR: line should start with a tab: " PR c++/101783"
> ERR: line should start with a tab: " * tree.c (cp_build_qualified_type_real): Excluding typedef from error"
> ERR: line should start with a tab: " PR c++/101783"
> ERR: line should start with a tab: " * g++.dg/parse/pr101783.C: New test."
It might work better to attach the output of git format-patch.
Also, your commit subject line is too long, at 83 characters: It must be
under 75 characters, and preferably closer to 50. I might shorten it to
c++: cv-qualified ref introduced by typedef [PR101783]
> * tree.c (cp_build_qualified_type_real): Excluding typedef from error
A change description in the ChangeLog should use present tense
("Exclude"), have a period at the end, and line wrap at 75 characters
like the rest of the commit message. So,
* tree.c (cp_build_qualified_type_real): Exclude typedef from
error.
> + ([dcl.type.decltype]),in which case the cv-qualifiers are ignored.
> + */
We usually don't put */ on its own line.
Jason
next prev parent reply other threads:[~2021-10-01 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6LXBsdU3xULuu8B3cEDGbcpHUXxF4roCC-zboWmtpGoPdVvw@mail.gmail.com>
2021-09-27 1:31 ` nick huang
2021-09-28 19:51 ` Jason Merrill
2021-09-30 18:24 ` nick huang
2021-10-01 13:29 ` Jason Merrill [this message]
2021-10-01 15:10 ` Nick Huang
2021-10-01 15:45 ` Jason Merrill
2021-10-01 19:52 ` Nick Huang
2021-10-05 19:40 ` Jason Merrill
2021-08-10 5:36 [PATCH] c++: Fix unnecessary error when top-level cv-qualifiers is dropped [PR101783] nick huang
2021-08-28 11:54 ` [PATCH] c++: Suppress error when cv-qualified reference is introduced by typedef [PR101783] nick huang
2021-09-24 20:33 ` Jason Merrill
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=7ff72053-60e7-3c9b-3737-458ec40f1f77@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickhuang99@hotmail.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).