public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/47583] [4.6 Regression] Inquire affected by previous read Date: Wed, 09 Feb 2011 15:48:00 -0000 [thread overview] Message-ID: <bug-47583-4-suqHjsRA4k@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47583-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47583 --- Comment #13 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> 2011-02-09 15:47:26 UTC --- There is some debate whether or not I did this properly. I was rushing last night, cobbled the PR number in the email subject, omitted the patch to the mailing list, left the pr number off the Changlog entry ... I hope I did not break the build and I apologize for any inconveniance I caused. I posted this here because I do not have regular email at my work location which is quite remote at the moment. Cheers everyone and I will do better next time. ;) (The service is free, as in free beer)
prev parent reply other threads:[~2011-02-09 15:47 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-01 21:53 [Bug fortran/47583] New: " harald at klimachs dot de 2011-02-01 22:17 ` [Bug fortran/47583] " kargl at gcc dot gnu.org 2011-02-02 3:09 ` [Bug fortran/47583] [4.6 Regression] " jvdelisle at gcc dot gnu.org 2011-02-02 6:04 ` harald at klimachs dot de 2011-02-02 6:15 ` harald at klimachs dot de 2011-02-02 7:12 ` jpr at csc dot fi 2011-02-02 8:04 ` harald at klimachs dot de 2011-02-02 10:03 ` jakub at gcc dot gnu.org 2011-02-02 12:48 ` jpr at csc dot fi 2011-02-03 5:36 ` pault at gcc dot gnu.org 2011-02-09 5:31 ` jvdelisle at gcc dot gnu.org 2011-02-09 6:12 ` jvdelisle at gcc dot gnu.org 2011-02-09 6:37 ` jvdelisle at gcc dot gnu.org 2011-02-09 7:05 ` harald at klimachs dot de 2011-02-09 15:48 ` jvdelisle at gcc dot gnu.org [this message]
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-47583-4-suqHjsRA4k@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).