preparing migration from baz to bzr

[John A Meinel]

Aaron Bentley wrote:
> John A Meinel wrote:
>
>>>Well, we certainly could support a "--clobber" option. Which would let
>>>you say "I want the published branch to look *exactly* like this one,
>>>don't concern yourself with what it actually looks like now".
>
>
> But...but...we already have that!  See --overwrite :-)
>

I was meaning in the official, builtin (non rsync) version of "bzr
push".  I have no problem using --overwrite.

My idea is that "bzr push" should work almost identical to "bzr pull"
just with the idea of from and to reversed.

The current bzr push is actually more of a "bzr publish". It just checks
to make sure the action is sensible, and then makes the remote tree look
like the local one (using rsync). A real bzr push would check the
ancestry, so that you can push into a tree, even if revision-history
doesn't match, and when it was done, revision-history still wouldn't
match, but the final revision would be the same.

The only difference is that "--overwrite" would also completely rewrite
the revision-history file, making it the same as the local file.

John
=:->

> Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20051019/c42bd17e/attachment.pgp