bzr.dev rsync copy is broken?

[Wouter van Heyst]

On Tue, Mar 28, 2006 at 10:11:03AM +0000, William Dode wrote:
> On 28-03-2006, William Dode wrote:
> > On 28-03-2006, Martin Pool wrote:
> >> We could remove the working tree, but then it won't be so useful as a
> >> way to bootstrap a new copy of bzr.  In any case removing it would
> >> require upgrading to a metadir format, which would make it impossible to
> >> pull down using bzr 0.7.
> >>
> >> As an interim measure perhaps we can set up a cron job that will revert
> >> it.  There is still a race window where someone might get an out-of-date
> >> working tree.
> >>
> >> Robert, would it be possible to make the public mirror pull from the
> >> pqm-maintained branch, so that pull could update the working tree?
> >>
> >> Updating the working tree over sftp would be pretty useful.
> >>
> >
> > What about a different command than pull to update a working tree ?  
> 
> i wanted to say instead of push...
> 
> >
> > bzr export sftp:... | ftp:... | rsync:...
> >

Export is there, but it needs some work before it can export to remote
filesystems. While I would like to see that happen anyway, I do think
push should be able to update working tree too.

Wouter van Heyst