Re: git annotate runs out of memory

From: Jason Sewall <jasonsewall@gmail.com>
Date: Dec 11, 2007, 19:27 UTC
Message-ID: <31e9dd080712111127h72ca18a4o574f3e65ff1acb16@mail.gmail.com>
In-Reply-To: <4aca3dc20712111103s1af3b045h484ea749378c6282@mail.gmail.com>

On Dec 11, 2007 2:03 PM, Daniel Berlin <dberlin@dberlin.org> wrote:

Show 7 quoted lines

> It is stored in an easier format. However, can you not simply provide
> side-indexes to do the annotation?
>
> I guess that own't work in git because you can change history (in
> other scm's, history is readonly so you could know the results for
> committed revisions will never change).
>

I don't know how other scms work, but history is definitely readonly in git - whatever sha1 you have that describes a commit was calculated based on its ancestor commits.

If you have a commit's id, it will *always* refer to the same thing - a tree state and its complete ancestry.

$ 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.