commit-performance and iter_changes

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Collins wrote:
> So, we've wanted to use iter_changes for commit for some time

Actually, I thought we'd given up hope on that long ago.

> I see it working something like this:
> 
d>  - tree to commit builder interface is a delta - iter_changes basically
>  - on merge commits the commit builder is responsible for comparing the
>    merged-in-tree with the basis to determine what nodes need
>    last-changed fields updated

Seems like a reasonable plan.  It seems intuitively obvious that commit
should only care about files that have been changed.  I think we just
wanted to avoid having a different codepath for merge commits.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkZo7EACgkQ0F+nu1YWqI3SVQCfR16bcL2BwDvlWc9T5cMpITxi
RIMAoIJkV3cQSugG4KCewMhC5HObRNew
=RzRa
-----END PGP SIGNATURE-----