git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[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
Next: Johannes Schindelin
Message 1 of 10 in “[RFC] faking cvs annotate”
  1. Martin LanghoffDec 16, 2005
  2. Johannes SchindelinDec 16, 2005
  3. Martin LanghoffDec 16, 2005
  4. Linus TorvaldsDec 16, 2005
  5. Nicolas PitreDec 16, 2005
  6. Linus TorvaldsDec 16, 2005
  7. Nicolas PitreDec 16, 2005
  8. Junio C HamanoDec 16, 2005
  9. Eric WongDec 16, 2005
  10. Ryan AndersonDec 16, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.