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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,978f50245fc02645 X-Google-Attributes: gid103376,public From: John Cosby Subject: Re: Root of a GNAT problem (was: Gnat v3.05 bug or compilation problem Date: 1996/12/12 Message-ID: <32B01F8F.446B@cpmx.saic.com>#1/1 X-Deja-AN: 203710832 references: <58h301$gad@alfali.enst-bretagne.fr> <58h6n2$2hbi@info4.rus.uni-stuttgart.de> <32AD9D35.4D1@lmtas.lmco.com> <32AE0EDC.4D4B@bix.com> content-type: text/plain; charset=us-ascii organization: SAIC Orlando mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 3.0 (X11; I; OSF1 V3.2 alpha) Date: 1996-12-12T00:00:00+00:00 List-Id: Tom Moran wrote: > > If folks regularly cc-ed bug messages to report@gnat.com to c.l.a. then > a suitable thread or archive search could show what's been reported. It > would of course be up to user/readers to figure out whether a particular > report was relevant to them. Not just that - one of our guys was downloading the source for GNAT yesterday because he couldn't find any other way of finding out if a bug was fixed. A link from the ACT page to a list of bug reports, with the version of GNAT that fixes the corresponding bugs, would be nice and save lots of download time. John -- John Cosby SAIC Orlando John.D.Cosby@cpmx.saic.com (407) 282-6700 x216