On Tue, Dec 9, 2008 at 12:51 AM, Hans Hübner <span dir="ltr">&lt;<a href="mailto:hans@huebner.org">hans@huebner.org</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

The ECL patches unfortunately are against the last release version, so<br>
we will not be able to include them in the upcoming release which will<br>
be based on the development version. &nbsp;Hopefully, someone can supply us<br>
with a new change set for ECL after the release.</blockquote></div><br>Could someone update either <a href="http://www.weitz.de/hunchentoot/">http://www.weitz.de/hunchentoot/</a> or <a href="http://weitz.de/patches.html">http://weitz.de/patches.html</a> to this effect?<br>
<br>A short message explaining where the development branch of Hunchentoot is (or how to coordinate development) would have been very helpful. Even a message like &quot;We&#39;re not accepting patches for Hunchentoot/this version is obsolete&quot; would be nice, or at the very least, a &quot;please check with the mailing list before writing any code targetting Hunchentoot&quot;.<br>
<br>I spent a fair amount of time porting ECL to Hunchentoot (and porting Hunchentoot&#39;s dependencies to ECL) only to discover it was wasted efforts in a similar way. Having some big friendly letters explaining how to get this &quot;development version&quot; on the Hunchentoot website would have saved my time, and clearly others.<br>