X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+YA7SyGu8qT5dR8ggMzkOjo3MR1Ul5iSs3BKYxe1qAQ=; b=S/jBiWrrrarTjn/J/nnMMGgcYaHcsqyjvIdOmSCm8w3OeK/RAGWu9HDDnrVs2mJm2Z o1M6beo7+W42w2sCDlKOfH2nXgBNkNk6ftij7bbHVFaJZYPkFBz2RHLxsrBrsAPngPFv 2lGIWjlAFDcZ0XjZNzHEI5u9lIv2/DX97xAoo6ngU8KWtUEG9ZBf4cuGZcpjjiN/KsDl qqsl+FaBA6NBUIS8a+MiTG4YXJLhWTXUZz6Cbav6T9/D7Msh8RmjTHoYLn8YvTlDr31E w42wJ+ZfBidTqCCjAiEscd7687/rvQfaCcl3SDyHrC3AylftNGdWOcDuDZw/N+qmGjiB 8xyw== MIME-Version: 1.0 X-Received: by 10.50.43.134 with SMTP id w6mr11593487igl.32.1445093265867; Sat, 17 Oct 2015 07:47:45 -0700 (PDT) In-Reply-To: <56225991.6040209@gmx.de> References: <5611566C DOT 4020507 AT iki DOT fi> <561A4BCE DOT 7050606 AT iki DOT fi> <56213FE2 DOT 7090409 AT iki DOT fi> <562168C6 DOT 5050001 AT gmx DOT de> <5621D433 DOT 2020004 AT iki DOT fi> <201510170455 DOT t9H4tQuZ007926 AT envy DOT delorie DOT com> <56225991 DOT 6040209 AT gmx DOT de> Date: Sat, 17 Oct 2015 17:47:45 +0300 Message-ID: Subject: Re: Random compile errors under WIndows (32 bit Windows Vista and Windows 10) From: "Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" To: djgpp AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 10/17/15, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote: > Am 17.10.2015 06:55, schrieb DJ Delorie: >>> So guess we should actually release 2.05 now. >> [...] > a) now it is 15:45 here in germany. I will wait until 21:00 (local time) > to see if Ozkan has committed his DXE module patch as presented in: > > > I do not want to apply it because I do not know if that is really the > final version. If I see that he has not committed the patch, then this > feature will definitively __NOT__ be part of the 205 release. I never got any response, so I am still waiting. The patch is final as far as I would implement it. So, here I ask: - Should I apply dxe patch to CVS HEAD? - Should I apply dxe patch to CVS v2_05_1 branch? -- O.S.