🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.gcc.bug
Article #768

Please send complete bug reports

#768
From: rms
Date: Sun, 29 Oct 1989 04:23
16 lines
1259 bytes
The purpose of bug-gcc is to transfer bug reports to the people who
maintain GCC.  In order to be useful for this purpose, a bug report
must contain a COMPLETE test case.  It is usually impossible to
construct a usable test case from a few "relevant lines", and the
whole rest of the function is probably relevant anyway.

People who aren't GCC maintainers are welcome to read the list.  But
they shouldn't forget that the list doesn't exist for their sake.  If
they don't receiving the contents of the list, then they should get
off it.  They should not ask the users to send incomplete bug reports
for their sake.

Please, if you have a GCC bug to report, send a complete
self-contained test case that can be run straight off to reproduce the
bug.  If you can easily shorten the test case without making the bug
go away, then go ahead; but otherwise, send the whole thing.
Technical Details
Message-ID: <8910290423.AA10773@sugar-bombs.ai.mit.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AI.MIT.EDU!rms

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AI.MIT.EDU!rms
From: rms@AI.MIT.EDU
Newsgroups: gnu.gcc.bug
Subject: Please send complete bug reports
Message-ID: <8910290423.AA10773@sugar-bombs.ai.mit.edu>
Date: 29 Oct 89 04:23:45 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 16