This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Jeremy Sanders <jss@ast.cam.ac.uk> writes: > On Sat, 23 Aug 2003, Andreas Jaeger wrote: > >> Jeremy Sanders <jss@ast.cam.ac.uk> writes: >> >> > Should bugs on the mainline be put into bugzilla? >> >> Yes - and please read http://gcc.gnu.org/bugs.html, we really need a >> complete case that reproduces this, > > It wasn't clear to me how to file mainline bugs. Maybe some text could be > added to bugs.html to say which version number to file under (I take it I > should file under 3.4?) Two alternatives: - Use the glibcbug script that you just build, it will fill this in - Use 3.4 in the web interface > Also, if I file a preprocessed file with the copyright belonging to > someone else, and the comments have been removed (by cpp), do I need to > include the copyright somewhere in the bug? The code is GPLd. I don't think so. But we would appreciate if you could destill a testcase out of the source so that instead of the preprocessed source, you would sent a really small testcase that exhibits the problem. Thanks, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Attachment:
pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |