Hi, * Theodore Tso [07-03-06 16:54:59 -0500] wrote:
Hmm.... the way I was planning on handling the performance bottleneck was to use "hg manifest --debug <rev>" and diffing the hashes against its parents. Using "hg manifest" only hits .hg/00manifest.[di] and .hg/00changelog.[di] files, so it's highly efficient. With the --debug option to hg manifest (not needed on some earlier versions of hg, but it seems to be needed on the latest development version of hg), it outputs the mode and SHA1 hash of the files, so it becomes easy to see which files were changed relative to the revision's parent(s).
I started getting/looking at hg a few days ago, mainly at the source only so that I likely miss some things...
Hmm. I'll need to further read the hg source to see how they do it. I now switched to defaulting to use the hg changes for normal changesets and the full manifest for merges. That's a huge boost already. Your approach sounds even better... so that I'll use it. :)
bye, Rocco -- :wq! - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html