File History vs. Path History

[Paul Mensonides]

On Sun, 20 Jan 2013 15:13:32 -0600, Matt Mackall wrote:

> On Sun, 2013-01-20 at 08:41 +0000, Paul Mensonides wrote:

>> Okay, so (thinking out loud) I can get all of the heads in the
>> repository, build a graph of the changesets via parents, run hg stat
>> --changes each changeset, build an entity index with the "history" that
>> I want, and serialize the entire thing.  Later, updating requires only
>> checking last used heads against current heads and only processing the
>> changesets back to those already processed.  Doesn't sound terribly
>> fun, but it's doable.
> 
> If you're going to throw some 'real' code at the problem, you might
> consider parsing and inverting 'hg debugindex path/to/file'.

Thanks for the tip.  I have prototyped something already that essentially 
maps the whole repository, but I have yet to do the caching/serialization--
which I have to do because it is quite inefficient on a repository of any 
significant size (primarily because I'm making many popen() calls to hg 
from C++ which is, of course, process creation, etc.).

Regards,
Paul Mensonides