public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bdavis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/19216] list directed read with leading slash Date: Sat, 01 Jan 2005 03:41:00 -0000 [thread overview] Message-ID: <20050101034103.25452.qmail@sourceware.org> (raw) In-Reply-To: <20050101033803.19216.bdavis@gcc.gnu.org> -- What |Removed |Added ---------------------------------------------------------------------------- Summary|formatted read with leading |list directed read with |slash |leading slash http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19216
next prev parent reply other threads:[~2005-01-01 3:41 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-01 3:38 [Bug libfortran/19216] New: formatted " bdavis at gcc dot gnu dot org 2005-01-01 3:41 ` bdavis at gcc dot gnu dot org [this message] 2005-01-01 3:42 ` [Bug libfortran/19216] list directed " pinskia at gcc dot gnu dot org 2005-01-06 14:43 ` [Bug libfortran/19216] list directed read with leading slash (NIST FM923) tobi at gcc dot gnu dot org 2005-04-15 8:59 ` fxcoudert at gcc dot gnu dot org 2005-04-18 7:05 ` cvs-commit at gcc dot gnu dot org 2005-04-18 7:18 ` [Bug libfortran/19216] [4.0 only] " fxcoudert at gcc dot gnu dot org 2005-05-30 15:17 ` kargl at gcc dot gnu dot org 2005-06-01 11:17 ` [Bug libfortran/19216] " fxcoudert at gcc dot gnu dot org 2005-06-02 5:45 ` fxcoudert at gcc dot gnu dot org 2005-06-16 22:51 ` cvs-commit at gcc dot gnu dot org 2005-06-16 23:01 ` cvs-commit at gcc dot gnu dot org 2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org 2005-06-18 23:19 ` pinskia 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=20050101034103.25452.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).