This is the mail archive of the gcc-patches@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]

Re: Patch: One version number to rule them all


Daniel Berlin writes:

> > There's a conversion script on gcc.gnu.org which massages the mail
> > submissions for use with bugzilla. 
> 
> Which is a massively ugly hack and is sure to stop working at some
> point, and i won't be able to fix it.
> Just FYI :)

But right now it works well enough, and I don't see a completely unrelated
patch as enough justification to remove what we have now.

> >  It works fine (more or less), and
> > gccbug is the only way to submit bugs via email, so please keep it around.
> 
> 
> I hate to say it, but this just isn't good enough of a reason.
> 
> we get 1-2 bugs via email a month.
> 
> Except for the ones by long time emailers, of them don't contain
> approriate info for reproducing the bug, and often end up getting closed
> because the person never later attaches preprocessed source.
> 
> 
> Or they attempt to paste 1 meg of preprocessed source into the email,
> whch is just as bad.

So you suggest that gccbug invites bad bug reports?  I don't buy this; it's
just as easy to create useless reports via a web front end.  On the other
hand, why seriously inconvenience those long time emailers (which, I might
add, usually produce complete and useful reports) for no particular reason?
This might well loose some of them completely, which would be a shame.

Besides, I think the GNU Coding Standards still call for a way to submit
bug reports via email, and gccbug provides a useful framework for this.

	Rainer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]