https://bugs.winehq.org/show_bug.cgi?id=38636
--- Comment #7 from Michael Tiller michael.tiller@gmail.com --- Anastasius,
(In reply to Anastasius Focht from comment #6)
Hello folks,
since you already mentioned bug 38272 in comment #1 the chance was pretty much 100% of being an exact dupe.
It may very well be that these bugs are duplicates. I am not at all familiar with Wine so I have no way of making that determination. The fact that both bugs happen to involve Go is, to me, hardly a basis for claiming that there is a "100% of being an exact dupe". They deal with completely different aspects of the Go runtime (clocks vs. http).
I'm not arguing with you that they are dupes. As I said, I'm not expert enough to say. But I am arguing with your implication here that reporting this bug separately was a waste of time and/or sloppy on my part. Think about it this way, if somebody comes along and has a problem with Python do you want them to say "Oh, I see there is another bug in here about Python, but for a program that is doing something completely different...It must be the same bug". They will either not report it or they'll add it on to some other issue for which it is completely inappropriate and confusing. It is much easier to mark one ticket as a duplicate of another than it is to sort out the confusion of multiple people arguing about multiple bugs under the same ticket.
It takes time to localize an issue and create reproducible bug reports. If you think it is a dupe, then mark it so. But don't blame people who are reporting the bug for not knowing enough about the internals of WINE to completely triage the issues.
We all have a role to play in this eco-system. I did my best to do my part and minimize confusion rather than jumping to conclusions based on my limited knowledge.