Re: [PATCH 3/3] verify-commit: scriptable commit signature verification

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 27, 2014, 18:55 UTC
Message-ID: <xmqqsimq18t0.fsf@gitster.dls.corp.google.com>
In-Reply-To: <53AD76C3.3060702@drmicha.warpmail.net>

Michael J Gruber <git@drmicha.warpmail.net> writes:

> ... or an extension <ref>^{mergetag} to our machinery, defaulting to the
> tag object containing the mergetag for the 2nd parent, with an optional
> version <ref>^{mergetag}<n>?

One thing you should not forget is that with mergetag, the original tag object is not even necessary to exist in the repository, and often the original tag will not be propagated to the general public.

You _could_ extract the necessary information from the commit that merges a signed tag to recreate the tag, but for what purpose? Your "$commit^{mergetag}<n>" needs to recreate the named tag object but it is unclear to me how you envision it to be used.

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