When checking out or updating a working-copy of the 42,000 file Mozilla tree, it
takes about a minute to do the "post-update" revision-bumping of every file.
Performance issues aside, it's really disconcerting for the user to see a
million file changes zoom by, then the phrase "Updated/Checked out revision N",
but then just hang there -- no prompt. The user wonders if the program has
crashed, or something. There's no indication that post-update-bumping is going on.
We need to print some sort of message like, "Finalizing working copy...", or
"Bumping local revision numbers...", and *then*, when the bumping is complete,
print "Updated/checked out revision N."
I have no idea how easy or hard this task is... but I'm filing it so I don't
forget about it. It would be great if someone investigated this (or even did