On 8/23/21 3:46 PM, Stefan Kanthak wrote:
> Gabriel Ravier <gabrav...@gmail.com> wrote:
>
>> On 8/22/21 11:22 PM, Stefan Kanthak wrote:
>
> [ 2bugzilla | !2bugzilla ]
>
>>> You (and everybody else) if free to use GCC bugzilla.
>>> Everybody and me is but also free NOT to use GCC bugzilla.
>>>
>>> Stefan
>>
>> Yes, you are free not to use the GCC Bugzilla. And GCC developers are
>> free to prefer to see bug reports be made to the GCC Bugzilla, as it is
>> the place dedicated to GCC bug reports, made specifically for that
>> purpose and with the infrastructure to handle it.
>>
>> What would you think if you had a Github or a Gitlab repository and some
>> people felt the need to randomly e-mail you about bugs they found
>> instead of filing them using the dedicated Issues system there ? And
>> what would you say if, upon being recommended to use that system, they
>> said that they are "free not to use" the system dedicated to helping
>> them reporting bugs when reporting bugs ? To me, that would just sound
>> rude and like they don't actually want to help find and fix bugs.
>
> That's a VERY WILD and of course RUDE SPECULATION:
> 0. I'm old school, I don't use git-something.
> 1. I explicitly invite everybody who reads my web pages or uses code I
>    publish there to send bug reports, comments, feedback, flames, ...
>    per mail!
> Before you ask: I receive quite some mail from complete strangers, even
> bug reports.

If you want an example that does not involve git: Let us assume some of your users started to randomly use rather impractical means of reporting bugs to you, like sending you letters or randomly accosting you in the street about them. It would be possible to try and handle those bugs, but would you not try to redirect those users to more practical means of making bug reports ?

Note that *you* may find e-mail to be a practical way of handling bug reports, but from what I know, the GCC development team have found that impractical and much less efficient than using a bug tracker, especially on such a huge project as GCC: if all the bugs that are reported on the Bugzilla were instead reported here and all the discussion about them was done here, then today there would have been no less than:
- 12 e-mails about new bugs, and
- 159 e-mails relating to existing bugs

>
> I consider the statement on <https://gcc.gnu.org/lists.html>
>
> | gcc is a high volume list for general development discussions about GCC.
> | Anything relevant to the development or testing of GCC and not covered
>   ~~~~~~~~~~~~~~~~~~~~~~~~                ~~~~~~~~~~~~~~
> | by other mailing lists is suitable for discussion here.
>
> as such an invitation too.

While this might imply in some way that this mailing list might be appropriate for this purpose, would it have taken that much time to also take a look at the GCC homepage ? The sidebar has an entire "Bugs" section, including a link literally called "How to report", which states directly to "Please submit your bug report directly to the GCC bug tracker." and links to https://gcc.gnu.org/bugzilla/

>
> Stefan
>
> JFTR: do you consider your wild speculations to be on-topic here?

I suppose I should apologize: I did not intend to make any accusations here. I simply could not think at the time of any other reasons why you would be so hostile to the idea of using Bugzilla (when you've been explicitly told that sending issues to the mailing list is close to equivalent to sending them to /dev/null) and, not being a native English speaker, I must have formulated the message more aggressively than I intended. I also had been rather angered by you saying "You should better implement such missing optimisations your users might expect from a mature compiler" which I misinterpreted (at least, I hope so) as being some kind of threat.

Reply via email to