public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/20811] gfortran include problem (regression from g77) Date: Thu, 07 Apr 2005 16:45:00 -0000 [thread overview] Message-ID: <20050407164512.6614.qmail@sourceware.org> (raw) In-Reply-To: <20050407143027.20811.afranck@gmx.de> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-07 16:45 ------- Confirmed. -- What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO| |19292 nThis| | Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |rejects-valid Last reconfirmed|0000-00-00 00:00:00 |2005-04-07 16:45:11 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20811
next prev parent reply other threads:[~2005-04-07 16:45 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-07 14:31 [Bug fortran/20811] New: " afranck at gmx dot de 2005-04-07 16:45 ` pinskia at gcc dot gnu dot org [this message] 2005-08-16 16:41 ` [Bug fortran/20811] " bsp at kithrup dot com [not found] <bug-20811-1270@http.gcc.gnu.org/bugzilla/> 2005-11-01 21:24 ` tobi at gcc dot gnu dot org 2005-11-04 17:22 ` mesmith dot 15507218 at bloglines dot com 2005-11-04 17:24 ` mesmith dot 15507218 at bloglines dot com 2005-11-04 17:30 ` mesmith dot 15507218 at bloglines dot com 2005-11-15 12:31 ` fxcoudert at gcc dot gnu dot org 2005-11-16 9:09 ` fxcoudert at gcc dot gnu dot org 2005-11-17 12:51 ` fxcoudert at gcc dot gnu dot org 2005-11-17 20:51 ` andreast at gcc dot gnu dot org 2005-11-17 21:30 ` andreast at gcc dot gnu dot org 2005-11-18 12:40 ` fxcoudert at gcc dot gnu dot org 2005-11-18 12:42 ` fxcoudert at gcc dot gnu dot 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=20050407164512.6614.qmail@sourceware.org \ --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).