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: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Root of a GNAT problem (was: Gnat v3.05 bug or compilation
 problem
Date: 1996/12/11
Message-ID: <dewar.850343181@merv>#1/1
X-Deja-AN: 204498436
references: <dewar.849335191@merv> <58h301$gad@alfali.enst-bretagne.fr>
 <58h6n2$2hbi@info4.rus.uni-stuttgart.de> <dewar.850182311@merv>
 <32AD9D35.4D1@lmtas.lmco.com> <32AE0EDC.4D4B@bix.com>
organization: New York University
newsgroups: comp.lang.ada
Date: 1996-12-11T00:00:00+00:00
List-Id: <comp.lang.ada>


Tom Moran says

"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."

please do NOT cc comments to report@gnat.com to any other mailing list
or newsgroup. Send a separate message, otherwise we cannot process the
report properly. Thanks. We should probably emphasize this in the documentation
I will update it right away.