From: Marek Polacek <polacek@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: where is PRnnnn required again?
Date: Tue, 6 Jul 2021 17:36:21 -0400 [thread overview]
Message-ID: <YOTM1Qm1dt4KnKfv@redhat.com> (raw)
In-Reply-To: <dbc6476e-6600-56c7-2997-7bf28053f6f0@gmail.com>
On Tue, Jul 06, 2021 at 03:20:26PM -0600, Martin Sebor via Gcc wrote:
> I came away from the recent discussion of ChangeLogs requirements
> with the impression that the PRnnnn bit should be in the subject
> (first) line and also above the ChangeLog part but doesn't need
> to be repeated again in the ChangeLog entries. But my commit
> below was rejected last Friday with the subsequent error. Adding
> PR middle-end/98871 to the ChangeLog entry let me push the change:
>
> https://gcc.gnu.org/g:6feb628a706e86eb3f303aff388c74bdb29e7381
>
> I just had the same error happen now, again with what seems like
> a valid commit message. Did I misunderstand something or has
> something changed recently?
>
> Martin
>
> commit 8a6d08bb49c2b9585c2a2adbb3121f6d9347b780 (HEAD -> master)
> Author: Martin Sebor <msebor@redhat.com>
> Date: Fri Jul 2 16:16:31 2021 -0600
>
> Improve warning suppression for inlined functions [PR98512].
>
> Resolves:
> PR middle-end/98871 - Cannot silence -Wmaybe-uninitialized at
> declaration si
> te
> PR middle-end/98512 - #pragma GCC diagnostic ignored ineffective in
> conjunct
> ion with alias attribute
This should be just
PR middle-end/98871
PR middle-end/98512
, no? Either here, or...
> gcc/ChangeLog:
...here.
> * diagnostic.c (get_any_inlining_info): New.
> (update_effective_level_from_pragmas): Handle inlining context.
> (diagnostic_enabled): Same.
> (diagnostic_report_diagnostic): Same.
> * diagnostic.h (struct diagnostic_info): Add ctor.
> (struct diagnostic_context): Add new member.
> * tree-diagnostic.c (set_inlining_locations): New.
> (tree_diagnostics_defaults): Set new callback pointer.
>
>
>
> Enumerating objects: 11, done.
> Counting objects: 100% (11/11), done.
> Delta compression using up to 16 threads
> Compressing objects: 100% (6/6), done.
> Writing objects: 100% (6/6), 3.37 KiB | 3.37 MiB/s, done.
> Total 6 (delta 5), reused 0 (delta 0)
> remote: *** The following commit was rejected by your
> hooks.commit-extra-checker script (status: 1)
> remote: *** commit: 8a6d08bb49c2b9585c2a2adbb3121f6d9347b780
> remote: *** ChangeLog format failed:
> remote: *** ERR: PR 98512 in subject but not in changelog: "Improve warning
> suppression for inlined functions [PR98512]."
> remote: ***
> remote: *** Please see:
> https://gcc.gnu.org/codingconventions.html#ChangeLogs
> remote: ***
> remote: error: hook declined to update refs/heads/master
> To git+ssh://gcc.gnu.org/git/gcc.git
> ! [remote rejected] master -> master (hook declined)
> error: failed to push some refs to
> 'git+ssh://msebor@gcc.gnu.org/git/gcc.git'
>
Marek
next prev parent reply other threads:[~2021-07-06 21:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 21:20 Martin Sebor
2021-07-06 21:36 ` Marek Polacek [this message]
2021-07-06 21:44 ` Martin Sebor
2021-07-06 22:09 ` Jonathan Wakely
2021-07-07 16:39 ` Martin Sebor
2021-07-07 20:42 ` Jonathan Wakely
2021-07-07 21:35 ` Martin Sebor
2021-07-07 21:53 ` Marek Polacek
2021-07-07 22:18 ` Martin Sebor
2021-07-07 22:24 ` Jonathan Wakely
2021-07-07 22:58 ` Martin Sebor
2021-07-07 23:03 ` David Malcolm
2021-07-08 8:26 ` Jonathan Wakely
2021-07-08 18:58 ` Martin Sebor
2021-07-07 22:15 ` Jonathan Wakely
2021-07-07 23:38 ` Martin Sebor
2021-07-07 17:51 ` Jakub Jelinek
2021-07-07 19:01 ` Martin Sebor
2021-07-07 21:01 ` 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=YOTM1Qm1dt4KnKfv@redhat.com \
--to=polacek@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@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).