X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Recipient: dj AT delorie DOT com Message-ID: <5543CB2D.7070903@iki.fi> Date: Fri, 01 May 2015 21:51:25 +0300 From: Andris Pavenis User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: DJ Delorie , djgpp AT delorie DOT com Subject: Re: GCC 5.1.0 problem with References: <201504280005 DOT t3S05t2U020439 AT delorie DOT com> <201504281718 DOT t3SHIpWZ009266 AT envy DOT delorie DOT com> <55434021 DOT 4010606 AT iki DOT fi> <5543C6E6 DOT 4090709 AT iki DOT fi> <201505011838 DOT t41Icjxw030105 AT envy DOT delorie DOT com> In-Reply-To: <201505011838.t41Icjxw030105@envy.delorie.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com On 05/01/2015 09:38 PM, DJ Delorie wrote: > Do you have a setup that can build the 2.05 release files? I don't at > the moment, but if you do we can use those zips. > I'm actually building all packages including sources from CVS version under Linux and after that rebuild binary packages natively. What we should do with source copyright notices. nmalloc could be a spacial case as we cannot ask author any more but original copyright text includes DJGPP license and LGPL as 2 choices. My tools for generating source packages do not touch copyright notices, One should also tag release in CVS Andris