Re: Commit ID in exported Tar Ball

From: Shawn O. Pearce <spearce@spearce.org>
Date: May 20, 2007, 03:57 UTC
Message-ID: <20070520035752.GG3141@spearce.org>
In-Reply-To: <7vd50wv88t.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:

Show 6 quoted lines

> René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> 
> > Something like the following patch?  Since we're already embedding the
> > commit ID in a comment, we might as well offer creating a synthetic file
> > for it, too, if that solves a user's problem that might be difficult to
> > work around otherwise.

What about being able to get the output of git-describe embedded into an archive file? Doesn't git.git do that in its Makefile? ;-)

git-describe is more human-friendly than a SHA-1...

-- 
Shawn.

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