X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<557078B1.9040004@iki.fi>
Date:	Thu, 04 Jun 2015 19:11:29 +0300
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <djgpp AT delorie DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: DJGPP v2.05: some thoughts
References:	<55673F0B DOT 1090103 AT iki DOT fi> <83twuwwshg DOT fsf AT gnu DOT org> <55675040 DOT 9030008 AT iki DOT fi> <556F6E49 DOT 8010006 AT gmx DOT de> <556FCCDF DOT 7080005 AT iki DOT fi> <83bngvr0ef DOT fsf AT gnu DOT org>
In-Reply-To:	<83bngvr0ef.fsf@gnu.org>
Reply-To:	djgpp AT delorie DOT com

On 06/04/2015 05:52 PM, Eli Zaretskii (eliz AT gnu DOT org) wrote:
>> Date: Thu, 04 Jun 2015 06:58:23 +0300
>> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi)" <djgpp AT delorie DOT com>
>>
>>> How is this supposed to work?
>>> I would like to give it a try with the next ports.
>>>
>> I guess we must at first create a CVS branch for DJGPP 2.05.
>>
>> Wide character related changes could after that be committed to trunk.
> I'm confused: didn't you suggest to include this in v2.05?  If so, why
> not commit it to the v2.05 branch to begin with?
>
>
Yes, I suggested it and posted suggestion to get some feedback. I took however Your notice that it 
would change building other packages into account. I guess we need to get 2.05 out (2.03 is simply 
already too ancient) and we do not need another eternal beta. That's why I would prefer not to 
integrate changes into 2.05.

Andris

- Raw text -