random thought of the day - a progress bar for tree transforms ?

[John A Meinel]

Aaron Bentley wrote:
> Robert Collins wrote:
> | Aaron,
> |     you may have done this already, but what do you think of the idea of
> | tree transform operations accepting a progress bar?
> 
> Yeah, we could do that.  Off the top of my head, there are four phases:
> 1. transform creation (calculating the build, revert or merge operation)
> 2. resolution of filesystem conflicts (this may run 1 to 10 times)
> 3. application of removals (renames, deletions, unversioning)
> 4. application of insertions (renames, creations, versioning)
> 
> I suspect that your average transform spends most of its time in 2.
> 
> Aaron

How do you get '1-10' times? It just realizes that it could conflict
that many times? Or are you just saying "this could run repeatedly".

It would be really nice to have transform have a progress bar, since in
a pull you tend to get a progress, and then all goes silent for quite
some time.

I'm thinking that if it is a fixed number of iterations, just do the
progress as 14 steps, and skip ones you don't use.
But it might be nicer to have an idea how many files you are checking,
and iterate over that instead.

(That, and we need to figure out why branch doesn't do anything for
quite some time, it doesn't seem to be CPU or bandwidth bound during
that time, probably latency bound).

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/20060214/84eb287b/attachment.pgp