Yuck.. why would anyone want to "upgrade" to my old and never declared
stable Squid-2.3 tree these days???
The note from the top of my page for the old Squid-2.3-hno tree says all
I think... <url:http://devel.squid-cache.org/hno/patch-2.3.html>
NOTE: I have not tested the Squid-2.3 version as
throughtfully as the Squid-2.2.STABLE5-hno releases
(more like not at all), and it is known that for
example async-io will not perform that well compared
to 2.2.STABLE5-hno. Most of these patches have been
incorporated into the main Squid distribution since
Squid-2.4 and I no longer actively maintain this
patchset.
And the another more recent note from the old page describing my "devel"
tree explains this further
<url:http://devel.squid-cache.org/hno/patch-devel.html>:
NOTE: This information is mostly outdated. For current
developments see http://devel.squid-cache.org where
development is now done in a more cooperative manner,
and due to the higher degree of openness in the Squid
development the need for these "personal" pages no
longer exists. The page still exists for reference
purposes as not all my old patches have made it into
the the new development model yet, but will eventually
go away completely.
The current Squid version is Squid-2.5, and there really is absolutely
no reason to upgrade to any older version. This is also the version
which is actively maintained any bugfixed, and assumed you are running
if asking questions on Squid-users.
Regards
Henrik Nordström
The author of the now obsolete -hno Squid versions
Michael Cloutier wrote:
>
> I recently upgraded my Squid to Version 2.3.STABLE4-hno.CVS on SuSE Linux
> 7.1 and I have developed a problem with my user authentication.
Received on Thu Jan 02 2003 - 12:56:46 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:12:25 MST