From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Hin-Tak Leung <htl10@users.sourceforge.net>,
git@vger.kernel.org, rene.scharfe@lsrfire.ath.cx
Subject: Re: git-archive's wrong documentation: really write pax rather than tar
Date: Wed, 3 Aug 2011 20:00:54 -0600 [thread overview]
Message-ID: <20110804020054.GA1947@sigill.intra.peff.net> (raw)
In-Reply-To: <7v62me6ism.fsf@alter.siamese.dyndns.org>
On Wed, Aug 03, 2011 at 06:56:41PM -0700, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > It might be a bit more obvious to find if we actually had a
> > --no-pax-header option, though.
>
> Yeah, we would need to make sure that --no-pack-header causes a barf
> for other backends, though. "struct archiver_args" right now seems to have
> compression_level but I think it should just have "const char **" that is
> interpreted by backends.
Actually, it is relevant for zip, too. The option should really be
called "--no-commit-id" or something similar. I don't think it's as big
a deal with zip (because there is no compatibility issue), but you may
want to omit the header for other reasons (e.g., because you know it
doesn't point to a commit that is public).
-Peff
next prev parent reply other threads:[~2011-08-04 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 22:17 git-archive's wrong documentation: really write pax rather than tar Hin-Tak Leung
2011-08-04 1:41 ` Jeff King
2011-08-04 1:56 ` Junio C Hamano
2011-08-04 2:00 ` Jeff King [this message]
2011-08-04 2:25 ` Junio C Hamano
2011-08-04 2:29 ` Jeff King
2011-08-04 17:39 ` René Scharfe
2011-08-04 2:13 ` Jeff King
2011-08-04 22:51 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2011-08-04 17:27 (unknown) Hin-Tak Leung
2011-08-04 17:54 ` git-archive's wrong documentation: really write pax rather than tar René Scharfe
2011-08-04 18:33 ` Hin-Tak Leung
2011-08-06 18:57 ` René Scharfe
2011-08-10 3:08 ` Hin-Tak Leung
2011-08-10 19:55 ` 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=20110804020054.GA1947@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=htl10@users.sourceforge.net \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).