On tor, 2008-07-03 at 23:39 +1200, Amos Jeffries wrote:
> My future plans there involve more standards compliance, which may make
> things harder for people if there are two code versions to look at. The
> upcoming compat changes from 3.2+ may also impact as non-portable back
> to Squid-2.
The bigger reason NOT to drop the tools from Squid-2 imho..
The main goal is forward, not backward.
I do not mind at all seeing changes in the Squid-3 version of the tools
not getting backported to Squid-2.
As I see it there is two choices:
a) Split the tools out completely, make them live their own life outside
of the main Squid repository.
b) Keep as-is.
My favorite is 'b'. The goal is after all that Squid-2 should slow down
as Squid-3 picks up speed.
REgards
Henrik
This archive was generated by hypermail 2.2.0 : Thu Jul 03 2008 - 12:00:03 MDT