On Wed, 17 Nov 2004, Visolve Squid Development Team wrote:
> We would like to work on making squid-3.0 version to STABLE one. We are
> planning to start this work by porting squid-2.5 patches ( c coding ) to
> squid-3.0 patches ( c++ coding ). How to collect patches needs to be
> ported to Squid-3.0.
Excellent!
You find the patches in bugzilla by querying for
Status: New, Open, Reopened (the default)
Target Milestone: 3.0
Status Whiteboard: PATCH25
http://www.squid-cache.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&target_milestone=3.0&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=PATCH25&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Bug+Number&field0-0-0=noop&type0-0-0=noop&value0-0-0=
It is recommended to where possible use the published Squid-2.5 patch
rather than the working copy attached to the bug reports. Sometimes
patches is improved slightly when applied to the release.
http://www.squid-cache.org/Versions/v2/2.5/bugs/
look for the bugzilla numbers aquired above
When you have ported a patch to Squid-3.0, attach it to the corresponding
bugzilla report and change priority to P1.
Regards
Henrik
Received on Sun Nov 21 2004 - 08:44:54 MST
This archive was generated by hypermail pre-2.1.9 : Tue Nov 30 2004 - 12:00:03 MST