Date: Sun, 29 Sep 1996 10:20:15 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "John M. Aldrich" <fighteer AT cs DOT com>
Cc: Charles Sandmann <sandmann AT clio DOT rice DOT edu>,
        DJGPP Workers Mailing List <djgpp-workers AT delorie DOT com>
Subject: Re: 'Cannot open'
In-Reply-To: <324B3876.2A5E@cs.com>
Message-Id: <Pine.SUN.3.91.960929101740.20703J-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 26 Sep 1996, John M. Aldrich wrote:

> Is it a good idea to mention this problem in the batch file's report, or
> can I assume that it will be corrected in a later DJGPP version?

IMHO, you should mention it, for those who have `djverify' but still work 
with binaries from DJGPP releases where the stub still had this bug.

> Alternatively, should I wait to release djverify until Charles releases
> the corrected stub, and use that instead of the v2.0 one?

It's a simple one-liner to correct it, so you might as well correct it 
now on your machine.