Date: Mon, 17 Jan 2000 16:50:07 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Bash 2.03 prerelease now available
In-Reply-To: <200001171446.QAA24230@is.elta.co.il>
Message-ID: <Pine.SUN.3.91.1000117164807.24187B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 17 Jan 2000, Mark E. wrote:

> You might try reporting the Autoconf related problems to the autoconf 
> list. The maintainer that released Autoconf 2.13 was rather indifferent to 
> fixing problems like these. I only managed to get a fix or two in. He 
> recently quit and now three new maintainers handle Autoconf. I'm familiar 
> with two of the names, and I'm almost certain we'll get better results 
> from the new maintainers.

Thanks for the suggestion.  In my experience, the maintainers usually 
want to see a specific solution to solve the problems.  Unfortunately,
I am not familiar enough with Autoconf to propose a solution.  Perhaps
someone else could do it.