bzr push, working directory, bzrtools

[John A Meinel]

Matthieu Moy wrote:
> Hi,
> 
> I've updated my bzr, and noticed there was now a native "bzr push". I
> suppose the one in bzrtools can now be removed.
> 
> The push command doen't create a working directory. The documentation
> should mention the way to re-create this working directory when the
> user has a local access to the push location.
> 
> It seems "revert" does the trick. Perhaps there's a better way.
> 

Robert and I have been discussing if "bzr push" should modify the
working directory when it is available. (I recently create a patch for
creating branches without working directories, for cases like a
published repository, which doesn't need them).

I believe Robert was working on some way to make the bzrtools' push
either not load itself if it finds the builtin one, or somehow add
functionality to it (copy the files using rsync rather than plain sftp
for instance). I'm not sure where he got on this.

For recreating the working tree, I believe revert is the only method
currently implemented.

John
=:->


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051102/4af91e80/attachment.pgp