From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Pierre Habouzit <madcoder@debian.org>, git@vger.kernel.org
Subject: Re: [PATCH v2] parse-opt: migrate builtin-checkout-index.
Date: Fri, 17 Oct 2008 16:58:23 -0700 [thread overview]
Message-ID: <7v63nqg4f4.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20081016132810.GG536@genesis.frugalware.org
Miklos Vajna <vmiklos@frugalware.org> writes:
> +static int option_parse_z(const struct option *opt,
> + const char *arg, int unset)
> +{
> + line_termination = unset;
> + return 0;
> +}
> ...
> + { OPTION_CALLBACK, 'z', NULL, NULL, NULL,
> + "paths are separated with NUL character",
> + PARSE_OPT_NOARG, option_parse_z },
This adds a new feature to say --no-z from the command line, doesn't it?
And I suspect the feature is broken ;-).
> + OPT_BOOLEAN(0, "stdin", &read_from_stdin,
> + "read list of paths from the standard input"),
> ...
> + argc = parse_options(argc, argv, builtin_checkout_index_options,
> + builtin_checkout_index_usage, 0);
> + state.force = force;
> + state.quiet = quiet;
> + state.not_new = not_new;
> + if (argc && read_from_stdin)
> + die("--stdin must be at the end");
Is this comment still correct? Do the original and your version act the
same way when the user says "checkout --stdin -f", for example? I suspect
the original refused it and yours take it (and do much more sensible
thing), which would be an improvement, but then the error message should
be reworded perhaps?
next prev parent reply other threads:[~2008-10-17 23:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 22:55 [PATCH] parse-opt: migrate builtin-checkout-index Miklos Vajna
2008-10-16 8:23 ` Pierre Habouzit
2008-10-16 13:28 ` [PATCH v2] " Miklos Vajna
2008-10-17 23:58 ` Junio C Hamano [this message]
2008-10-18 1:17 ` [PATCH] " Miklos Vajna
2008-10-19 18:30 ` Miklos Vajna
2008-10-19 18:31 ` Miklos Vajna
2008-10-19 20:11 ` Junio C Hamano
2008-10-19 20:19 ` Pierre Habouzit
2008-10-19 20:59 ` Junio C Hamano
2008-10-19 19:29 ` Raphael Zimmerer
2008-10-19 19:34 ` Pierre Habouzit
2008-10-19 21:45 ` Junio C Hamano
2008-10-18 15:54 ` [PATCH v2] " Pierre Habouzit
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=7v63nqg4f4.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
--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;
as well as URLs for NNTP newsgroup(s).