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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Received: by 2002:a5e:c80b:: with SMTP id y11mr4570012iol.20.1549394212006; Tue, 05 Feb 2019 11:16:52 -0800 (PST) X-Received: by 2002:a9d:117:: with SMTP id 23mr24878otu.5.1549394211657; Tue, 05 Feb 2019 11:16:51 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!news.muarf.org!nntpfeed.proxad.net!feeder2-2.proxad.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!k10no28569itk.0!news-out.google.com!v141ni34ita.0!nntp.google.com!k10no28563itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 5 Feb 2019 11:16:51 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.168.19.89; posting-account=O_NgcgoAAABs6pgCjroQBmOBL5ZZGPUc NNTP-Posting-Host: 85.168.19.89 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> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Yet another gnat bug From: George Shapovalov Injection-Date: Tue, 05 Feb 2019 19:16:51 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:55444 Date: 2019-02-05T11:16:51-08:00 List-Id: On Monday, February 4, 2019 at 5:11:51 PM UTC+1, Simon Wright wrote:=20 > > 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. >=20 > 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 limitat= ions.. > AdaCore do respond to reports on FSF GCC there, especially if the report > is about the GCC build system or about bad code generation.=20 Oh, they do? Thanks for the info! That's not something I directly thought about, as the problem is with the u= pstream (of FSF), so it makes sense to take it directly to upstream (the mo= st common reaction of many projects and distibutions is to first try to fig= ure out if its them or upstream, and if its upstream, then its universally = - "report it to upstream". Which is totally logical, in avoiding messy dupl= ication of effort. In fact it is often not something they would even have c= ontrol over). So, I just took it directly to upstream, strictly following the procedure d= escribed in the bug message :). > 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 g= et around to it.=20 But to the credit of AdaCore, they react quickly - I already got a confirma= tion that they got it and will look into it..