delorie.com/archives/browse.cgi | search |
From: | "Mark E." <snowball3 AT bigfoot DOT com> |
To: | Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>, djgpp-workers AT delorie DOT com |
Date: | Mon, 14 Aug 2000 17:43:27 -0400 |
MIME-Version: | 1.0 |
Subject: | Re: Problems with depcomp from fileutils 4.0x & bash 2.03 |
Message-ID: | <39982FBF.32711.231F56@localhost> |
In-reply-to: | <399853B0.631A9BC8@phekda.freeserve.co.uk> |
X-mailer: | Pegasus Mail for Win32 (v3.12c) |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> down to bash 2.03 (thanks guys!). This is actually a problem earlier > encountered in the djgpp-workers thread "Porting problems with Sh-utils > (beta)" - the first mail is dated Sat, 8 Apr 2000 18:49:49 +0500 on my > system. This is occasionally to gnu.bash.bug. The Bash maintainer's response always is that the construct is working as intended. > Thankfully this problem does not exist in bash 2.04 beta 5c. Are there any > plans to fix this problem in bash 2.03? I have no plans for an update to Bash 2.03 to change this behavior. But if the real Bash maintainer decides to release a patch for this, I'll apply it and release an update. Also, I'll be releasing Bash 2.04 "real soon now" unless any more problems are reported. Mark
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |