Peter Memishian <peter.memish...@sun.com> writes: > > > Just 'hg log' or, for instance 'hg log -v'? > > > > Ah, of course. Yes, he's got log's default arg list set to -v. That > > mostly shouldn't be necessary now, with the ON hgstyle file he's using, > > which does spit out the full description, rather than just the first line > > (though the list of files isn't part of it; maybe that's what he's looking > > for). > > Ah -- I'd forgotten I'd done that -- thanks Rich and Danek! > > Still, a lot of times when I'm digging with "hg log" I actually want to > see the file list (i.e., I'll know the file of interest when I see it), so > I still find "-v" performance important. Is "hg log -v" just inherently > slow (i.e. unusable) on large repos?
Danek and I talked about this some more. The cause here is the style file delivered by SUNWonbld and configured by our hgsetup(1), which sets the template for printing changesets to include the name of any changed file, and the manner in which it changed (for the sake of outgoing -v, and RTIs). This information is comparatively expensive to retrieve (the way in which a file changed is not stored in a changeset, only its path), so when you do 'hg log -v' using that style file, you're doing the equivalent of calling 'hg status' across each pair of revisions, or at present about 10,200 times. A defaultly configured mercurial only lists the path names on 'hg log -v' and requires --debug to show the manner of change. Presumably because it takes so long. -- Rich _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
