From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Yet another gnat bug Date: Tue, 05 Feb 2019 20:37:16 +0000 Organization: A noiseless patient Spider Message-ID: References: <987a6ff2-32d0-45a0-b90a-be9fbf1ff47b@googlegroups.com> <048a6dce-ee26-4850-a1db-980fef58e8a2@googlegroups.com> <2qb5E.172675$592.78651@fx16.am4> <1af84a62-9236-403e-a87b-59f1a82cb3a5@googlegroups.com> <24o5E.235692$IF1.229991@fx03.am4> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="e2d5c901c5b3fdbb76ba9b7fa6e10fc0"; logging-data="24586"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+QCirJpe7Lnx6Zx7L8yQF1h2PeEQbzbII=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (darwin) Cancel-Lock: sha1:/DcX/v2hIpcJsccmJASgVxNcy+Q= sha1:NjfRPTUkA2FUiilkOBUhhUMvLFU= Xref: reader01.eternal-september.org comp.lang.ada:55445 Date: 2019-02-05T20:37:16+00:00 List-Id: George Shapovalov writes: > On Monday, February 4, 2019 at 5:11:51 PM UTC+1, Simon Wright wrote: >> > I chatted with them briefly 2 days ago on Fosdem and they told me that >> > they prefer an email report and that tracker is not really functional >> > for a community version at least. >> >> Do you mean the GCC Bugzilla? I can quite understand why reports >> against just GNAT CE wouldn't really be appropriate there. > No, I meant the tracker mentioned on the bug message: >>GAP members can alternatively use GNAT Tracker: | >>| http://www.adacore.com/ section 'send a report'. > > From his reaction I took it that that tracker is not that > active. Althopugh it would not be so usefull for many people anyway, > if it has usage limitations.. If you have a contract with AdaCore then Tracker is the point of contact; and the response when I worked for a comapny with a contract was terrific. If not, your only direct contact is report@adacore.com (with GNAT in the subject line). >> AdaCore do respond to reports on FSF GCC there, especially if the report >> is about the GCC build system or about bad code generation. > Oh, they do? Thanks for the info! > That's not something I directly thought about, as the problem is with > the upstream (of FSF), so it makes sense to take it directly to > upstream (the most common reaction of many projects and distibutions > is to first try to figure out if its them or upstream, and if its > upstream, then its universally - "report it to upstream". Which is > totally logical, in avoiding messy duplication of effort. In fact it > is often not something they would even have control over). So, I just > took it directly to upstream, strictly following the procedure > described in the bug message :). The AdaCore people working on FSF GCC are the same people working on the 'upstream' product, which is why I've never thought of it like that; but I see your point. And, I've occasionally added 'same problem with GNAT CE' to Bugzilla reports where I thought it might stimulate interest. >> Personally I like to report on Bugzilla where appropriate, because >> reports to report@adacore.com aren't publicly visible. I don't know how >> annoying it'd be to report in both places. > Yes, that's indeed a concern. This is why I created that github > project, as I had a few bugs lying around already. I'll populate it > with more when I get around to it. > But to the credit of AdaCore, they react quickly - I already got a > confirmation that they got it and will look into it.. It helps if they know you!