From: Junio C Hamano <gitster@pobox.com>
To: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 5/6] archive: allow --exec and --remote without equal sign
Date: Fri, 25 Jul 2008 17:31:57 -0700 [thread overview]
Message-ID: <7vmyk5pjsy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1216982486-5887-6-git-send-email-rene.scharfe@lsrfire.ath.cx> (Rene Scharfe's message of "Fri, 25 Jul 2008 12:41:26 +0200")
Rene Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
> Convert git archive to parse_options(). The parameters --remote and --exec
> are still handled by their special parser. Define them anyway in order for
> them to show up in the usage notice.
>
> Note: in a command like "git archive --prefix --remote=a/ HEAD", the string
> "--remote=a/" will be interpreted as a remote option, not a prefix, because
> that special parser sees it first. If one needs such a strange prefix, it
> needs to be specified like this: "git archive --prefix=--remote=a/ HEAD"
> (with an equal sign).
>
> Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
> ---
> archive.c | 110 +++++++++++++++++++++++++++++++++++++-----------------------
> 1 files changed, 68 insertions(+), 42 deletions(-)
Hmph, somewhat dubious.
The real point of parse-options was to make the code smaller, easier to
maintain and command line handling more consistent. At least this patch
seems to fail on the two out of three counts.
All of the other patches made obvious sense to me and are queued for -rc1
but I'd like to backburner this one.
next prev parent reply other threads:[~2008-07-26 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 10:41 [PATCH 1/6] archive: add write_archive() Rene Scharfe
2008-07-25 10:41 ` [PATCH 2/6] archive: move parameter parsing code to archive.c Rene Scharfe
2008-07-25 10:41 ` [PATCH 3/6] archive: define MAX_ARGS where it's needed Rene Scharfe
2008-07-25 10:41 ` [PATCH 4/6] archive: declare struct archiver " Rene Scharfe
2008-07-25 10:41 ` [PATCH 5/6] archive: allow --exec and --remote without equal sign Rene Scharfe
2008-07-25 10:41 ` Rene Scharfe
2008-07-25 10:54 ` René Scharfe
2008-07-26 0:31 ` Junio C Hamano [this message]
2008-07-26 7:09 ` PATCH 6/6] archive: convert,to parse_options() [was: [PATCH 5/6] archive: allow --exec and --remote without equal sign] René Scharfe
2008-07-26 0:28 ` [PATCH 5/6] archive: allow --exec and --remote without equal sign Junio C Hamano
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=7vmyk5pjsy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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).