Michael Olson <[EMAIL PROTECTED]> writes: > I think I'm going to try writing an incremental parser for the > dvc-log output. The new git-log code, in particular, feels > unacceptably slow.
BTW, there's another option: * Use git-rev-list, and parse its output. You get a skeleton ewoc structure, and you can start displaying it (you'll get only the "commit ..." lines. * Use stg like "git-show --pretty=fuller" to get the complete info about revisions. You can divide the list of revisions into paquets of ~10 to 50 to minimize the overhead of launching several processes, and complete the log buffer little by little. That way, the portion of the log which appears on screen comes more or less immediately. Indeed, we have something like this for baz, it keeps a cache (both on disk and in memory) of the revision information. Before going for either approach, we should think about how to achieve the same results with other back-ends keeping the code well factored. In particular, I don't think bzr and hg have a command equivalent to "git rev-list" (but we can ask the user to install a plugin that creates one, or contribute one to upstream perhaps). -- Matthieu _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
