------- Comment #5 from rguenth at gcc dot gnu dot org 2009-08-09 12:08 ------- IMHO all fields on http://gcc.gnu.org/bugzilla/enter_bug.cgi need a link to documentation just like some already have. We can't expect people to guess what to put there.
The alternative is to remove some of the fields (but then they are undocumented and meaningless on the main bug page as well). As Andrew said most of the detail information can be guessed from the description. But sometimes it is really hard because people do not read bugs.html (which is in a sorry state) and even do not paste simple things like the output of running 'gcc -v' into the description. The http://gcc.gnu.org/bugzilla/enter_bug.cgi page should in its preamble mention that - you should create attachments for large testcases after submitting the initial report - bugzilla is not the proper way to submit patches (link to contribute.html) IMHO the http://gcc.gnu.org/bugzilla/enter_bug.cgi page misses the Known-to-work and Known-to-fail fields. IMHO the assign to, CC and bug dependency fields are not required for http://gcc.gnu.org/bugzilla/enter_bug.cgi. The build-triplet is the most confusing one and I would remove it retaining the host and target fields (with proper descriptions). The gcc.gnu.org/bugs.html needs serious TLC. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36739
