From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
git@vger.kernel.org
Subject: Re: [PATCH] Fix archive format with -- on the command line
Date: Thu, 10 Dec 2009 15:31:40 -0800 [thread overview]
Message-ID: <7vd42m8kyr.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vhbry8l54.fsf_-_@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu\, 10 Dec 2009 15\:27\:51 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Giving --format from the command line, or using output file extention to
> DWIM the output format, with a pathspec that is disambiguated with an
> explicit double-dash on the command line, e.g.
>
> git archive -o file --format=zip HEAD -- path
> git archive -o file.zip HEAD -- path
>
> didn't work correctly.
>
> This was because the code reordered (when one was given) or added (when
> the former was inferred) a --format argument at the end, effectively
> making it to "archive HEAD -- path --format=zip", i.e. an extra pathspec
> that is unlikely to match anything.
A side note to this issue is that
$ git add non-existing-path
complains but
$ git archive HEAD non-existing-path
doesn't. Is this something we should consider a bug, or a feature?
next prev parent reply other threads:[~2009-12-10 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 21:26 [BUG] git archive formats and dashdash Ilari Liusvaara
2009-12-10 22:05 ` Junio C Hamano
2009-12-10 22:22 ` Miklos Vajna
2009-12-10 22:42 ` Junio C Hamano
2009-12-10 23:27 ` [PATCH] Fix archive format with -- on the command line Junio C Hamano
2009-12-10 23:31 ` Junio C Hamano [this message]
2009-12-12 15:00 ` René Scharfe
2009-12-30 3:13 ` Nanako Shiraishi
2009-12-30 8:11 ` Junio C Hamano
2009-12-10 22:25 ` [BUG] git archive formats and dashdash Ilari Liusvaara
2009-12-10 22:20 ` [PATCH] builtin-archive: insert --format before double dash if necessary Miklos Vajna
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=7vd42m8kyr.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=vmiklos@frugalware.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