From: "René Scharfe" <l.s.r@web.de>
To: fuz@fuz.su, git@vger.kernel.org
Subject: Re: git archive should use vendor extension in pax header
Date: Tue, 26 Jan 2016 23:06:25 +0100 [thread overview]
Message-ID: <56A7EDE1.1020909@web.de> (raw)
In-Reply-To: <20160124155909.GA16847@fuz.su>
Am 24.01.2016 um 16:59 schrieb fuz@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.
This is only a problem if you don't know how a given tar files was
created (or modified later). How did you get into this situation? Or
in other words: Please tell me more about your use case.
> 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
This would be included in addition to the comment in order to avoid
breaking existing users, I guess.
If you have a random archive and want to know if it was generated by git
then your next question might be which options and substitutions were
used. That reminds me of this thread regarding verifiable archives:
http://article.gmane.org/gmane.comp.version-control.git/240244
Thanks,
René
next prev parent reply other threads:[~2016-01-26 22:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 15:59 git archive should use vendor extension in pax header fuz
2016-01-26 22:06 ` René Scharfe [this message]
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=56A7EDE1.1020909@web.de \
--to=l.s.r@web.de \
--cc=fuz@fuz.su \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).