Re: cvs commit: squid3 configure

2007-12-14 Thread Henrik Nordstrom
On lör, 2007-12-15 at 14:54 +1300, Amos Jeffries wrote: > Yes I applied the code by 'patch -p1'. Good. Then there is no risk of accidently backing out others edits. > I will need some help about adding the website /Versions/v3/3.1/ pages > and the release-3.1.sgml notes. What need to stay/go/ch

Re: cvs commit: squid3 configure

2007-12-14 Thread Amos Jeffries
Henrik Nordstrom wrote: On lör, 2007-12-15 at 12:00 +1300, Amos Jeffries wrote: Can everyone please hold off commits to squid3-HEAD for 36-48 hours. I don't want it to erase any work you have done. Thanks. Aren't you applying the changes using patch? Yes I applied the code by 'patch -p1'.

Re: cvs commit: squid3 configure

2007-12-14 Thread Henrik Nordstrom
On lör, 2007-12-15 at 12:00 +1300, Amos Jeffries wrote: > Can everyone please hold off commits to squid3-HEAD for 36-48 hours. I > don't want it to erase any work you have done. Thanks. Aren't you applying the changes using patch? Applying changes by copy is dangerous. There is up to a day dela

Re: cvs commit: squid3 configure

2007-12-14 Thread Amos Jeffries
Amos Jeffries wrote: Now that 3.0 is branched. (is it complete?) I'll be starting to import the new files for 3.1 in about 7-8 hours. Leaving the core code change until any post-release shakedown period has finished. Any objectsions to 3-5 days? OK, with the voting 2-earlier, 1-later and 2+ a

Re: cvs commit: squid3 configure

2007-12-14 Thread Amos Jeffries
Alex Rousskov wrote: On Fri, 2007-12-14 at 21:35 +0100, Henrik Nordstrom wrote: On fre, 2007-12-14 at 18:26 +1300, Amos Jeffries wrote: He suggested a big(ger) delay than a few days to wait for bugs to prevent 'inventing two patches for two branches'. My opinion: With SQUID_3_0 branched ther

Re: cvs commit: squid3 configure

2007-12-14 Thread Alex Rousskov
On Fri, 2007-12-14 at 21:35 +0100, Henrik Nordstrom wrote: > On fre, 2007-12-14 at 18:26 +1300, Amos Jeffries wrote: > > > He suggested a big(ger) delay than a few days to wait for bugs to > > prevent 'inventing two patches for two branches'. > > My opinion: > > With SQUID_3_0 branched there is

Re: cvs commit: squid3 configure

2007-12-14 Thread Henrik Nordstrom
On fre, 2007-12-14 at 18:26 +1300, Amos Jeffries wrote: > He suggested a big(ger) delay than a few days to wait for bugs to > prevent 'inventing two patches for two branches'. My opinion: With SQUID_3_0 branched there is no reason to hold back stuff from Squid-3 HEAD. Usually bugfixes is quite

Re: cvs commit: squid3 configure

2007-12-13 Thread Amos Jeffries
Amos Jeffries wrote: Now that 3.0 is branched. (is it complete?) I'll be starting to import the new files for 3.1 in about 7-8 hours. Leaving the core code change until any post-release shakedown period has finished. Any objectsions to 3-5 days? Weirdness...Adrians email to me has disappeared

Re: cvs commit: squid3 configure

2007-12-13 Thread Adrian Chadd
On Fri, Dec 14, 2007, Amos Jeffries wrote: > > Now that 3.0 is branched. (is it complete?) > > I'll be starting to import the new files for 3.1 in about 7-8 hours. > Leaving the core code change until any post-release shakedown period has > finished. > Any objectsions to 3-5 days? You can if you

Re: cvs commit: squid3 configure

2007-12-13 Thread Henrik Nordstrom
On fre, 2007-12-14 at 14:57 +1300, Amos Jeffries wrote: > Now that 3.0 is branched. (is it complete?) Yes. 3.0.STABLE1 is even published. > I'll be starting to import the new files for 3.1 in about 7-8 hours. > Leaving the core code change until any post-release shakedown period has > finished. >

Re: cvs commit: squid3 configure

2007-12-13 Thread Amos Jeffries
Now that 3.0 is branched. (is it complete?) I'll be starting to import the new files for 3.1 in about 7-8 hours. Leaving the core code change until any post-release shakedown period has finished. Any objectsions to 3-5 days? Amos