[MERGE] inode sorted stats in status

[Robert Collins]

So, I've implemented inode sorting for stats. It doesn't make a huge
difference that I can see, though I may just have trees where the disk
alphabetical order and the inode order match.

Its also only doing inode-within-a-dir optimisation.

I don't know if this is truely needed - I would love some feedback and
testing. Particularly *cold cache* testing.

In my testing, it shaves 2 seconds off cold-cache status of a mozilla
tree:

:!time ./bzr st ../test-repos/mozilla/ 

real    0m36.818s
user    0m3.552s
sys     0m1.252s

:!time ./bzr st ../test-repos/mozilla/

real    0m38.199s
user    0m3.640s
sys     0m1.188s

It doesn't seem particularly different on hot-cache operations.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: readdir-1749.patch
Type: text/x-patch
Size: 32613 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080820/1d5afe88/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080820/1d5afe88/attachment-0001.pgp