git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: tar commit header names

From
René Scharfe <rene.scharfe@lsrfire.ath.cx>
Date
Mar 29, 2007, 16:07 UTC
Message-ID
<460BE44B.8090301@lsrfire.ath.cx>
In-Reply-To
<Pine.LNX.4.64.0703261230420.6485@iabervon.org>
Daniel Barkalow schrieb:
> I'm entirely ignorant of pax header stuff, but would it be possible to 
> have the pax header specify which project this commit is from (which has 
> to come from a git-archive option, clearly).

Technically, yes. The commit ID is stored in a comment, more info could appended to it. Adding more stuff there would necessitate an ordering scheme, though. I'm not sure this is useful enough. There already is a nice convention on where to store the project name, description and URL: in a file named 'README'. :)

Show 5 quoted lines
> Also, could 
> git-get-tar-commit-id have an option to look for more pax headers beyond 
> the first? (I'm building tar files by appending multiple archives for 
> different projects from git-archive, and I suddenly find the embedded 
> commit id is helpful, and surprisingly inaccessible in this context.)

This could be done, at the cost of git-get-tar-commit-id having to be able to really parse tar files in order to seek to the end of the first and thus to the start of the appended one. Right now it simply reads the first few bytes, quickly checks if this looks like a tar file and prints the commit ID, if one is found.

The right place to add generic archive comment extraction capabilities (with multi-archive support) would be a general purpose archiver like GNU tar, no?

René
Previous: Daniel BarkalowNext: Daniel Barkalow
Message 2 of 3 in “tar commit header names”
  1. Daniel BarkalowMar 26, 2007
  2. René ScharfeMar 29, 2007
  3. Daniel BarkalowMar 29, 2007

Read the whole thread, see it on lore, or plain text.

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