[PLUGIN] bzr uncommit updated

[John A Meinel]

Robert Collins wrote:
> On Sun, 2005-09-25 at 01:11 -0400, Aaron Bentley wrote:
> 
>>..I've updated branch to take a --basis parameter.  When that is provided,
>>the texts, inventories and revisions from the basis revision are copied
>>into the new branch's stores, and the only data we copy from the remote
>>branch is the stuff we don't have.
> 
> 
> I've merged this into integration. Its a good hack ;0.
> 
> I think it would be nice though, to only copy the referenced revisions -
> and to validate them as we do when branching normally....  that is, to

I agree. I was branching something that was ultimately not related 
(bzrweb), but I wasn't sure that it wasn't related, so I used --basis. 
It ended up copying 1500 revisions, before downloading only the 54 that 
were in the history.

> simply do a normal fetch of the requested remote revision, and attempt
> retrieval of each revision locally before retrieving it remotely. This
> wouldn't be as fast, but would still be much faster than remote
> retrieval. A similar question will apply in the post weave world to copy
> or to validate.
> 
> Note that validating pre-weave doesn't imply not hardlinking.

You would just check first, and then hardlink, right?

Post weave gets trickier. Because a weave with extra data is still 
useful (so hardlinking is viable). Perhaps just only pulling the 
revisions that we need (since revision-store is not a weave), and then 
the inventory? Should we pull the full weave? I was thinking that for 
the individual texts, just pull the whole weave, but I don't know about 
the inventory.

John
=:->

> 
> Rob
> 
-------------- 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/20050928/256b613d/attachment.pgp