public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/39813] [feature request] __PRETTY_FUNCTION__ addition Date: Thu, 29 Sep 2011 17:03:00 -0000 [thread overview] Message-ID: <bug-39813-4-BRDYP3NDGW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39813-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39813 --- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-09-29 16:51:28 UTC --- Thanks for the explanation. I don't think you need to do anything since the mails still get through - but seeing the address removed from the CC list is certainly confusing.
next prev parent reply other threads:[~2011-09-29 16:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39813-4@http.gcc.gnu.org/bugzilla/> 2011-09-29 0:00 ` paolo.carlini at oracle dot com 2011-09-29 15:46 ` Joseph S. Myers 2011-09-29 15:48 ` Joseph S. Myers 2011-09-29 15:48 ` joseph at codesourcery dot com 2011-09-29 15:48 ` paolo.carlini at oracle dot com 2011-09-29 15:51 ` joseph at codesourcery dot com 2011-09-29 15:58 ` paolo.carlini at oracle dot com 2011-09-29 16:54 ` LpSolit at netscape dot net 2011-09-29 17:03 ` joseph at codesourcery dot com [this message] 2011-09-29 17:15 ` redi at gcc dot gnu.org 2012-08-18 18:58 ` [Bug c++/39813] improve __PRETTY_FUNCTION__ for templated methos lundberj at gmail dot com 2015-04-27 22:27 ` [Bug c++/39813] improve __PRETTY_FUNCTION__ for templated methods paolo.carlini at oracle dot com 2009-04-19 11:27 [Bug c++/39813] New: [feature request] __PRETTY_FUNCTION__ addition gcc at daryl dot haresign dot com 2009-12-29 14:55 ` [Bug c++/39813] " gcc at daryl dot haresign dot com
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-39813-4-BRDYP3NDGW@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).