Re: [RFC PATCH v2] builtin/shortlog: explicitly set hash algo when there is no repo

From: Wolfgang Müller <wolf@oriole.systems>
Date: Oct 16, 2024, 19:14 UTC
Message-ID: <4dnthnr3ksoirvltn4smfyasyl5g4edzznheuo7hji4zy7h7gn@uomlcpchbvar>
In-Reply-To: <ZxANnCw/yVzLl0yn@nand.local>

On 2024-10-16 15:01, Taylor Blau wrote:

> So that means that '%H', '%h', '%T', and '%t' are off the table. '%an'
> and '%ae' seem reasonable to implement, but '%aN' and '%aE' less so,
> because we don't have a .mailmap file to read. The same goes for the
> committer variants of all of those.

An interesting tidbit here is that git-shortlog(1) actually does read a .mailmap file when processing stdin, but it takes it from the current directory instead. Having read the full manual today, it's one of the only times it mentions a difference in behaviour regarding standard input.

-- 
Wolf

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