delorie.com/archives/browse.cgi | search |
From: | Martin Stromberg <eplmst AT epl DOT ericsson DOT se> |
Message-Id: | <200205311152.NAA13181@lws256.lu.erisoft.se> |
Subject: | Re: Patches for building with gcc 3.1 - tests chunk |
To: | djgpp-workers AT delorie DOT com (DJGPP-WORKERS) |
Date: | Fri, 31 May 2002 13:52:40 +0200 (MET DST) |
Cc: | pavenis AT lanet DOT lv |
In-Reply-To: | <3CF78B52.23724.61E62F@localhost> from "pavenis@lanet.lv" at May 31, 2002 02:40:18 PM |
X-Mailer: | ELM [version 2.5 PL3] |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Andris said: > Don't report them to gcc-bugs AT gcc DOT gnu DOT org. Go to Why not? <http://gcc.gnu.org/lists.html> says: "gcc-bugs is a relatively high volume list for bug reports and general discussion about bugs in GCC. " Should that list and/or text be removed? > http://gcc.gnu.org/gnats.html > and use web form to report a bug. In this case somebody will have to > close it. So it's rather likely it will be read. Yes. But if I'm not sure it's a bug I prefer to get some feedback on the matter. E. g. the useless warning about empty format string. If feedback won't be provided, I stop there. If they can't be bothered to read my questions, I can't be bothered to persue the matter. Right, MartinS
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |