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 c/22133] In MinGW trailling slash forward not allowed in include path Date: Thu, 07 Jul 2005 13:34:00 -0000 [thread overview] Message-ID: <20050707133413.7286.qmail@sourceware.org> (raw) In-Reply-To: <20050621020312.22133.ohommes@comcast.net> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-07 13:34 ------- *** Bug 20594 has been marked as a duplicate of this bug. *** -- What |Removed |Added ---------------------------------------------------------------------------- CC| |ericw at evcohs dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22133
next prev parent reply other threads:[~2005-07-07 13:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-21 2:03 [Bug c/22133] New: " ohommes at comcast dot net 2005-06-21 3:16 ` [Bug c/22133] " pinskia at gcc dot gnu dot org 2005-06-21 4:11 ` pinskia at gcc dot gnu dot org 2005-07-07 13:34 ` pinskia at gcc dot gnu dot org [this message] [not found] <bug-22133-10859@http.gcc.gnu.org/bugzilla/> 2007-04-05 18:16 ` pinskia at gcc dot gnu dot org 2007-04-10 9:58 ` amylaar at gcc dot gnu dot org 2007-04-10 13:12 ` eweddington at cso dot atmel dot com [not found] <bug-22133-4@http.gcc.gnu.org/bugzilla/> 2011-02-25 13:59 ` ktietz at gcc dot gnu.org 2011-10-02 10:25 ` paolo.carlini at oracle 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=20050707133413.7286.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).