[MERGE] Better progress reporting in commit
Ian Clatworthy
ian.clatworthy at internode.on.net
Tue Jun 19 08:58:37 BST 2007
One of my goals for 0.18 is to make commit faster. Following the
direction Rob is driving for each Use Case, the idea is to start at the
outermost layer, validate that the code is using the right high level
algorithm and abstractions, and progressively move any inefficiencies
into logical APIs on Tree, Branch & Repository. We can then address
those inefficiencies collectively via new file formats at the right time.
The attached patch is step 1 along this path. It cleans up the progress
monitoring in commit so that it no longer assumes we know the total size
of the tree. To be more explicit, we do know the total number of stages
in commit (and it's a stable number) so the progress reporting is "stage
centric" now. Within one of those stages, we report how many entries
we've processed so far. FWIW, the total entry count right now is still
the tree size. In the future though, we can adjust the upper number to
reflect partial commit file counts, smarter knowledge about just the
interesting/changed entries, etc.
All that background explanation aside, this patch makes the UI better
regardless. :-)
Ian C.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: commit-better-progress.patch
Type: text/x-patch
Size: 8932 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070619/74b8a44a/attachment.bin
More information about the bazaar
mailing list