Re: mod_proxy build instructions

[Chuck Murcko <ch...@topsail.org>]

Well, you should definitely update your local copy before you start. 8^)

A good rule is not to leave the module unable to build after checkins. So
whether you see changes or not, you'll be able to work. Just before 
committing, doing cvs up is useful to check for conflicts.

I always cvs up before a change to avoid getting stepped on, unless the
coast is clear of potential conflicts.

What are you and Victor planning? I feel badly that Victor has seen mostly proxy_ftp.c so far.

Chuck

On Thursday, March 8, 2001, at 08:18 PM, Graham Leggett wrote:

> Chuck Murcko wrote: 
>  
> > I'm about to rip the cache code out of the proxy, and Victor and I were 
> > going to go bug hunting in proxy_http.c. 
>  
> I was going to start working on that today (where today is in around 8 
> hours time - it's 02:16 where i am now. I'm stuck waiting for people to 
> deliver things at home - so I am a captive audience. I was going to 
> start with HTTP so as not to tread on Victor's toes with FTP. 
>  

Chuck Murcko
Topsail Group
http://www.topsail.org/