Re: [www/bugzilla] PR 36739 Proposal for clarifications in GCC Bugzilla

[Gerald Pfeifer <gerald at pfeifer dot com>]

On Sun, 9 Aug 2009, Manuel López-Ibáñez wrote:
> I am not sure how to test such patch but if the form gets broken in
> some way, we can always revert it.

Indeed, I'd proceed pragmatically here: apply the patch, test, and if
your testing fails (I am sure you'll have some bug to report), just
revert.

Based on the discussions so far, I'd propose the following:

 - keep the target triplet 
 - remove the build triplet
 - not sure about the host triplet, the target certainly is most important

 - keep Cc, which is really used not too rarely and we do not provide the
   full input to those Cc:ed if it happens in a second step

 - avoid <strong>
 - keep text to a minimum, but add a description for everything the
   user needs to fill in
(- specifically, simplify bugs.thml)

My position is that as long as your patch improves upon the status quo,
we shouldn't ask for perfection.  Well, we can ask for it, but not demand. 
:-)  So, I think a patch even if not covering all further suggestions for 
improvements you got is fine.

Thanks,
Gerald