public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jay dot krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44252] fixincludes fork vs. vms Date: Sun, 23 May 2010 10:33:00 -0000 [thread overview] Message-ID: <20100523103318.8578.qmail@sourceware.org> (raw) In-Reply-To: <bug-44252-16543@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from jay dot krell at cornell dot edu 2010-05-23 10:33 ------- Created an attachment (id=20729) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20729&action=view) trivial two line untested patch -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44252
prev parent reply other threads:[~2010-05-23 10:33 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-05-23 10:31 [Bug c/44252] New: " jay dot krell at cornell dot edu 2010-05-23 10:33 ` jay dot krell at cornell dot edu [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=20100523103318.8578.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).