www.delorie.com/archives/browse.cgi | search |
Date: | Tue, 12 Nov 2002 01:13:36 -0500 |
Message-Id: | <200211120613.gAC6Dar23534@envy.delorie.com> |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <002501c28a10$b1612a00$021ca8c0@helm> (message from 2boxers on |
Tue, 12 Nov 2002 00:59:41 -0500) | |
Subject: | Re: djcrx203.zip refresh (June 2002) |
References: | <10211120238 DOT AA21596 AT clio DOT rice DOT edu> <002501c28a10$b1612a00$021ca8c0 AT helm> |
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 |
> missing is updated documentation. As a result, the existing faq, > howto and readme's do little more than vaguely outline a process > that even the most The FAQ almost always lags behind releases. Mostly because you can't answer the frequently asked questions until they're frequently asked ;-) The READMEs that are inside the zips should be updated as needed, at least for factual information. The HOWTOs are independent, and rely on people *doing* those things to update them. So, the cross-build howto looks like it's yours ;-) The web site is usually updated right after a release, based on whatever docs got released.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |