public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de To: 25824@bugs.debian.org, cpbs@debian.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: other/6903: gcc could give better error message when /tmp gets full Date: Mon, 09 Dec 2002 14:14:00 -0000 [thread overview] Message-ID: <20021209221422.15451.qmail@sources.redhat.com> (raw) Synopsis: gcc could give better error message when /tmp gets full State-Changed-From-To: open->feedback State-Changed-By: cae State-Changed-When: Mon Dec 9 14:14:21 2002 State-Changed-Why: As Zack pointed out there's not much that gcc can do about this. Any objections if I close this one? regards Christian http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6903
next reply other threads:[~2002-12-09 22:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-09 14:14 ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 18:49 neroden 2002-06-01 16:06 Zack Weinberg 2002-06-01 15:46 Matthias Klose
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=20021209221422.15451.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=25824@bugs.debian.org \ --cc=cpbs@debian.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).