From: fuz@fuz•su
To: git@vger•kernel.org
Subject: git archive should use vendor extension in pax header
Date: Sun, 24 Jan 2016 16:59:09 +0100 [thread overview]
Message-ID: <20160124155909.GA16847@fuz.su> (raw)
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 reply other threads:[~2016-01-24 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 15:59 fuz [this message]
2016-01-26 22:06 ` git archive should use vendor extension in pax header René Scharfe
2016-01-27 23:25 ` fuz
[not found] ` <20160127114634.GA1976@fuz.su>
[not found] ` <56A92913.3030909@web.de>
2016-01-27 23:45 ` fuz
2016-01-28 8:13 ` Johannes Schindelin
2016-01-28 9:14 ` fuz
2016-02-06 13:23 ` René Scharfe
2016-02-06 14:57 ` fuz
2016-02-15 20:25 ` René Scharfe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160124155909.GA16847@fuz.su \
--to=fuz@fuz$(echo .)su \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox