[RFC] faking cvs annotate
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Dec 16, 2005, 01:13 UTC
- Message-ID
- <46a038f90512151713i118e58acia466d0f65ff91383@mail.gmail.com>
I know, I know, use pickaxe :-)
Any suggestions as to how to implement a not-too-slow annotate that looks reasonable enough so as to fool real cvs clients? Let's assume I'll have the "per-file-version numbers" to translate commit SHA1s into cvs-ish version numbers in a magic hat, right next to the fluffy bunnies.
Suggestions of GIT machinery that would shortcut the trip from
git-rev-list HEAD $path
to a annotate-ish output. Did I dream it or is qgit showing something annotate-ish in its screenshots?
Note! Just told a white lie: I won't be actually using git-rev-list. Instead, I'll have a rev list that will gloss over branched development, picking only one "path" of the history every time (initially using the algorithm formerly known as rand() ) , and showing merge commits as one.
cheers,
martin