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=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=2GNX14NrnPXFBCpPCtdPy74pPJb0mTaCusVsqqmF9Mw=;
        b=JQPi6TSO1jOy30c3nMZxUDhPAI2AQM2f4TmJNTyioKZw8o0gNqL8JDUD7dKbxImxkI
         udj6XGCmdkbEXWvh0swTfXymNTwNYE92czIcX1Am1alu8JfH57Zj2Vvb9MlLkzDrOAIi
         NSM9dTPjLHIxBY0JcADFUeawXNQWk8ARSGXoyos3ZEOIPijcOP2NrDxz8+EO0KgHNf+U
         HxuJyczS8iaZ5aBYpbfYD3udo0hrjus0kZ4sR48F8pWHPNiwVIQONonll7O7jt9xwyAg
         T0F7iIW9H+eo72BGgujvon/81cQPeOu+EcntI02zI4dqok0uGbUgQDgOkliYqs9mkj8B
         JsIA==
X-Received: by 10.129.131.214 with SMTP id t205mr15290449ywf.26.1435528930663;
        Sun, 28 Jun 2015 15:02:10 -0700 (PDT)
Message-ID: <55906EE1.2040403@gmail.com>
Date: Sun, 28 Jun 2015 18:02:09 -0400
From: "Frank Sapone (emoaddict15 AT gmail DOT com)" <djgpp AT delorie DOT com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: DJGPP v2.05
References: <558D18CE DOT 3070004 AT iki DOT fi>	<558ED38D DOT 1020602 AT iki DOT fi>	<a23efb52-57fb-4b51-8693-ec919e76089e AT googlegroups DOT com>	<8709a9e4-a90f-447e-8191-4deb6886f894 AT googlegroups DOT com>	<559056B9 DOT 9080307 AT gmail DOT com>	<CAA2C=vA0VunOxyDJ2pN8DdpmN83FXm01qpTaBmCFCY+CKzCeLg AT mail DOT gmail DOT com>	<55906739 DOT 1030400 AT gmail DOT com> <CAA2C=vDdaL6+y0zD_xGrm+LSPv4esd9-dGmg4VFW7Ay+PnWtAQ AT mail DOT gmail DOT com>
In-Reply-To: <CAA2C=vDdaL6+y0zD_xGrm+LSPv4esd9-dGmg4VFW7Ay+PnWtAQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

> I can look at it (it being q2dos yes?) as time permits. Do you prefer
> patches or forks + merge requests?
Forks, but I already fixed those warnings.  The only one remaining is 
related to an aggressive loop optimization.  I'm not too worried about 
it right now.

Frank