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!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.109.57.116.186.mobile.3.dk!not-for-mail From: Jacob Sparre Andersen Newsgroups: comp.lang.ada 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? Date: Sun, 06 May 2018 18:37:32 +0200 Organization: JSA Research & Innovation Message-ID: <87sh74u4dv.fsf@jacob-sparre.dk> References: <9c3a75d6-a01f-4cfa-9493-10b8b082ead8@googlegroups.com> <114db2c4-1e8c-4506-8d7c-df955dd9f808@googlegroups.com> <87d0yc1lsq.fsf@nightsong.com> <878t901jp4.fsf@nightsong.com> <670085384.547216974.759926.laguest-archeia.com@nntp.aioe.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: franka.jacob-sparre.dk; posting-host="109.57.116.186.mobile.3.dk:109.57.116.186"; logging-data="21912"; mail-complaints-to="news@jacob-sparre.dk" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:AmcSa/L31ZAVx0+adpPW7gjAEAY= Xref: reader02.eternal-september.org comp.lang.ada:52042 Date: 2018-05-06T18:37:32+02:00 List-Id: Simon Wright wrote: > Considering the timing, I'd think each GPL release is a bookmark (tag) > in the GNAT Pro repo, somewhat after the Pro=>FSF merge. This is also how I understand the process. Greetings, Jacob -- "There's a lot of information that was in the programmer's head when they wrote the code that isn't reflected in that code"