From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: fuz@fuz.su
Cc: git@vger.kernel.org
Subject: Re: git archive should use vendor extension in pax header
Date: Thu, 28 Jan 2016 09:13:03 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1601280906340.2964@virtualbox> (raw)
In-Reply-To: <20160127234512.GA5453@fuz.su>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi Robert,
[I am not going to re-Cc: the dropped email addresses; please note that it
is pretty much frowned upon on this mailing list if you do not
reply-to-all and might affect your conversation.]
On Thu, 28 Jan 2016, fuz@fuz.su wrote:
> On Wed, Jan 27, 2016 at 09:31:15PM +0100, René Scharfe wrote:
>
> > Users can always go back to the original format. At least I don't
> > expect this new format becoming the default too quickly.
This is the most crucial issue here, as far as I am concerned: there are
already tons of .zip files out there that were created by git archive, and
there will inevitably be loads of tons more *having the current pax header
format*.
So tools wanting to deal with Git archives will have to handle those as
well, i.e. do *precisely* as René suggested and use get-tar-commit-id. As
such, the value of changing the format *now* is a bit like closing the
barn's door after pretty much all of the horses left (except the old one
that has a few troubles getting up in the morning but that is too nice to
the kids to shoot).
> Sure thing. If this is going to be implemented, I would add options
> to choose what / what style of metadata to include.
Why not put your money where your mouth is? I.e. get your head down into
the code and come up with a patch (because otherwise it is unlikely that
your idea will go anywhere)?
Ciao,
Johannes
next prev parent reply other threads:[~2016-01-28 8:13 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
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 [this message]
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=alpine.DEB.2.20.1601280906340.2964@virtualbox \
--to=johannes.schindelin@gmx.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).