Re: SCM code changes status

2009-02-17 Thread Stefan Bodewig
On 2009-02-17, Stefan Bodewig bode...@apache.org wrote: On 2009-02-16, Stefan Bodewig bode...@apache.org wrote: I'll watch the next helios build and then try to merge trunk to live if it looks OK (I removed the directory sync feature by accident, so I better take a closer look). Yesterday

Re: SCM code changes status

2009-02-16 Thread sebb
On 16/02/2009, Stefan Bodewig bode...@apache.org wrote: Hi all, apart from some string constants that I want to extract (need to look up Python's idiom for constants) I'm now ready to move ahead - see the differences between svn revisions 741390 and 744799. I'll watch the next helios

Re: SCM code changes status

2009-02-16 Thread Stefan Bodewig
On 2009-02-16, Stefan Bodewig bode...@apache.org wrote: I'll watch the next helios build and then try to merge trunk to live if it looks OK (I removed the directory sync feature by accident, so I better take a closer look). Yesterday things looked fine. I have a merged live branch sitting on

Re: SCM code changes status

2009-02-16 Thread Stefan Bodewig
On 2009-02-16, sebb seb...@gmail.com wrote: On 16/02/2009, Stefan Bodewig bode...@apache.org wrote: In particular I want to make the updaters check whether an existing working copy is in fact a working copy for the configured URL - and blow it away if it isn't. The idea is to look into

SCM code changes status

2009-02-15 Thread Stefan Bodewig
Hi all, apart from some string constants that I want to extract (need to look up Python's idiom for constants) I'm now ready to move ahead - see the differences between svn revisions 741390 and 744799. I'll watch the next helios build and then try to merge trunk to live if it looks OK (I removed