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

git archive should use vendor extension in pax header

From
Ffuz@fuz.su <fuz@fuz.su>
Date
Jan 24, 2016, 15:59 UTC
Message-ID
<20160124155909.GA16847@fuz.su>
Right now, git archive creates a pax global header of the form
    comment=57ca140635bf157354124e4e4b3c8e1bde2832f1

in tar archives it creates. This is suboptimal as as comments are specified to be ignored by extraction software. It is impossible to find out in an automatic way (short of guessing) that this is supposed to be a commit hash. It would be much more useful if git created a custom key. As per POSIX suggestions, something like this would be appropriate:

    GIT.commit=57ca140635bf157354124e4e4b3c8e1bde2832f1
Please consider this suggestion.

Yours sincerely, Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments
Next: René Scharfe
Message 1 of 9 in “git archive should use vendor extension in pax header”
  1. fuz@fuz.suJan 24, 2016
  2. René ScharfeJan 26, 2016
  3. fuz@fuz.suJan 27, 2016
  4. fuz@fuz.suJan 27, 2016
  5. Johannes SchindelinJan 28, 2016
  6. fuz@fuz.suJan 28, 2016
  7. René ScharfeFeb 6, 2016
  8. fuz@fuz.suFeb 6, 2016
  9. René ScharfeFeb 15, 2016

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.