Message-Id: <199904051436.OAA79226@out2.ibm.net>
From: "Mark E." <snowball3 AT usa DOT net>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Mon, 5 Apr 1999 10:36:37 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Bash 2.03 updated March 22nd
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990405075030 DOT 23822C-100000 AT is>
In-reply-to: <Pine.SUN.3.91.990405105703.6045A-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> > before that.  So this problem came into existence somewhere between
> > the beginning of March and March 23rd.
> 
> Wasn't that time frame about the same as when you switched from Bash 2.02 
> to 2.03?  If so, could it be that the problem appeared in 2.03?
> 

My changelog says Feb. 19th.

BTW, does the problem start at the same check every time? And if you 
can, let me know if the problem still happens under a Win9x DOS box.

--- 
Mark Elbrecht, snowball3 AT usa DOT net
http://snowball.digitalspace.net/