Re: mercurial to git
- From
- Rocco Rutte <pdmef@gmx.net>
- Date
- Mar 6, 2007, 22:47 UTC
- Message-ID
- <20070306224747.GB42331@peter.daprodeges.fqdn.th-h.de>
- In-Reply-To
- <20070306215459.GI18370@thunk.org>
Hi,
* Theodore Tso [07-03-06 16:54:59 -0500] wrote:
Show 9 quoted lines
>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!