public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103758] bogus warning: misspelled term 'decl' in format; use 'declaration' instead [-Wformat-diag] Date: Fri, 17 Dec 2021 17:31:47 +0000 [thread overview] Message-ID: <bug-103758-4-u8V7nwZSTS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103758-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103758 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2021-12-17 Ever confirmed|0 |1 --- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> --- Agreed.
next prev parent reply other threads:[~2021-12-17 17:31 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-17 17:30 [Bug c++/103758] New: " mpolacek at gcc dot gnu.org 2021-12-17 17:31 ` jason at gcc dot gnu.org [this message] 2021-12-17 17:31 ` [Bug c++/103758] " mpolacek at gcc dot gnu.org 2021-12-17 19:27 ` mpolacek at gcc dot gnu.org 2022-01-03 21:27 ` cvs-commit at gcc dot gnu.org 2022-01-03 21:28 ` mpolacek at gcc dot gnu.org 2022-01-05 8:48 ` marxin at gcc dot gnu.org 2022-01-05 15:14 ` mpolacek at gcc dot gnu.org 2022-01-05 15:32 ` jakub at gcc dot gnu.org 2022-01-05 15:33 ` jakub at gcc dot gnu.org 2022-01-05 15:38 ` mpolacek at gcc dot gnu.org 2022-01-05 15:49 ` msebor at gcc dot gnu.org 2022-01-06 0:43 ` cvs-commit at gcc dot gnu.org 2022-01-17 18:33 ` cvs-commit at gcc dot gnu.org 2022-01-17 18:33 ` mpolacek at gcc dot gnu.org 2022-01-17 18:39 ` mpolacek at gcc dot gnu.org 2022-01-17 18:45 ` jakub at gcc dot gnu.org 2022-01-17 18:47 ` mpolacek at gcc dot gnu.org 2022-01-17 21:27 ` cvs-commit at gcc dot gnu.org
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=bug-103758-4-u8V7nwZSTS@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).