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
X-Received: by 2002:a6b:ce9:: with SMTP id
 102-v6mr17759907iom.134.1525529962370;
        Sat, 05 May 2018 07:19:22 -0700 (PDT)
X-Received: by 2002:a9d:24a1:: with SMTP id z30-v6mr232744ota.4.1525529961882;
 Sat, 05 May 2018 07:19:21 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.unit0.net!newsreader5.netcologne.de!news.netcologne.de!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!u74-v6no1187083itb.0!news-out.google.com!b185-v6ni3048itb.0!nntp.google.com!u74-v6no1187080itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Sat, 5 May 2018 07:19:21 -0700 (PDT)
In-Reply-To: <670085384.547216974.759926.laguest-archeia.com@nntp.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=47.185.233.194;
 posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo
NNTP-Posting-Host: 47.185.233.194
References: <9c3a75d6-a01f-4cfa-9493-10b8b082ead8@googlegroups.com>
 <114db2c4-1e8c-4506-8d7c-df955dd9f808@googlegroups.com>
 <87d0yc1lsq.fsf@nightsong.com>
 <a181b4df-ceec-4d3e-8669-19ee8f268e56@googlegroups.com>
 <878t901jp4.fsf@nightsong.com>
 <bb2cbfdf-abb3-4b59-9ded-ce27bb98144b@googlegroups.com>
 <pchk2s$co5$1@dont-email.me>
 <lyr2mrz8mx.fsf@pushface.org> <pci51h$uir$2@dont-email.me>
 <670085384.547216974.759926.laguest-archeia.com@nntp.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9d9da202-c60c-435b-9c79-a15642d1c55c@googlegroups.com>
Subject: Re: Precisely why can't official FSF GNAT maintainers copy bug fixes
 in GNAT & its GCC-contained runtime en masse from GNAT GPL Community Edition?
From: "Dan'l Miller" <optikos@verizon.net>
Injection-Date: Sat, 05 May 2018 14:19:22 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3117
X-Received-Body-CRC: 2568342154
Xref: reader02.eternal-september.org comp.lang.ada:52008
Date: 2018-05-05T07:19:21-07:00
List-Id: <comp.lang.ada>

On Saturday, May 5, 2018 at 7:44:54 AM UTC-5, Luke A. Guest wrote:
> Simon Clubley <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote:
>=20
> > Yes, that would be a far better way to put it, thanks.
> >=20
> > What I was trying to say was that there are two distinct versions
> > of the GNAT compiler and that changes are pushed in one direction only.
>=20
> It=E2=80=99s more likely to be three branches with the CODE flowing like:
>=20
> GNAT Pro -> GNAT GPL -> FSF GNAT

Yes, that is how I suspect that it is as well.

The question is where precisely historically did each of the files is the G=
NAT-Pro branch originate?  I suspect that even the oldest of these are file=
s whose rights to copy were assigned to FSF by NYU 1992 to 1993, likely pre=
dating even the formation of AdaCore (and its twin in France).  My suspicio=
n is that even AdaCore depends on the GMGPL (as any third party would) to l=
icense these NYU-authored files in the GNAT Pro branch, especially the olde=
st ones dating all the way back to NYU.  (Subsequent assignments of rights =
to copy to FSF =E2=80=A2might=E2=80=A2 have placed newer first-written-by-A=
daCore files in the same category too.)

Does anyone have a copy of the Air Force contract with NYU to write the Ada=
9X Project's compiler?