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

Re: [RFC] 1st pass at git-annotate (not-quite functional, however)

From
Junio C Hamano <junkio@cox.net>
Date
Jan 23, 2006, 08:24 UTC
Message-ID
<7vslrfz70f.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060123080532.GD19212@mythryan2.michonline.com>
Ryan Anderson <ryan@michonline.com> writes:
> I haven't figured out exactly how I want to handle annotating across
> merges,...

You might want to take a look at the "passing blames around" algorithm I did for "git blame" loooooooooooooooong time ago.

    http://article.gmane.org/gmane.comp.version-control.git/5483
Previous: Ryan Anderson
Message 2 of 2 in “[RFC] 1st pass at git-annotate (not-quite functional, however)”
  1. Ryan AndersonJan 23, 2006
  2. Junio C HamanoJan 23, 2006

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.