Re: [PATCH RFC 0/5] Introduce git-blame-tree(1) command

From: Junio C Hamano <gitster@pobox.com>
Date: May 15, 2025, 16:39 UTC
Message-ID: <xmqqa57d3k1d.fsf@gitster.g>
In-Reply-To: <aCXsKHiP4uIzCMrt@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> Curious. Isn't it exactly the same what git-blame(1) does though? Taken
> the textual representation of a tree object, we figure out when each of
> the lines has last been changed. That to me sounds like exactly the same
> thing as git-blame(1), but just for trees instead of for blobs.

That's mechanical worldview from the viewpoint of those who know the internal representation and workings of Git, I would have to say.

As an end-user, I view "where does the body of this function came from" and "when did I touch this file the last time" quite different and unrelated kind of queries.

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