From: Jeff King <peff@peff.net>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: git@vger.kernel.org
Subject: Re: Parse --o in format-patch
Date: Fri, 28 Jun 2013 12:31:53 -0400 [thread overview]
Message-ID: <20130628163153.GA9127@sigill.intra.peff.net> (raw)
In-Reply-To: <20130628160459.GA16832@paksenarrion.iveqy.com>
On Fri, Jun 28, 2013 at 06:05:00PM +0200, Fredrik Gustafsson wrote:
> I don't quite manage to figure out gits argv parsing and would need some
> help on the way.
>
> I want:
> git format-patch -o outdir HEAD~
>
> Work exactly the way it does now, setting output_directory to outdir.
> But I also want
> git format-patch -o HEAD~
>
> to set output_directory with a NULL value so that I can assign a default
> value to it. Is that even possible with the current argv-parsing implementation?
It's possible to have an "optional" argument by using the
PARSE_OPT_OPTARG flag. However, it is not backwards compatible from the
user's perspective, as they must use the "sticked" form:
git format-patch -ooutdir ...
to specify the argument. Otherwise, it is not clear in:
git format-patch -o outdir HEAD~
whether "outdir" is the argument to "-o", or if it is simply the next
argument.
However, if you are just interested in "turning off" a previously given
argument, we usually spell that with the "--no-" prefix to the long
option (e.g., "--no-output-directory" in this case).
I'm not clear how that interacts with your example, though. Your example
tries to use "-o" to set output_directory to NULL. But it is already
NULL if you do not specify any "-o" at all.
-Peff
next prev parent reply other threads:[~2013-06-28 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:05 Parse --o in format-patch Fredrik Gustafsson
2013-06-28 16:31 ` Jeff King [this message]
2013-06-28 16:44 ` Fredrik Gustafsson
2013-06-28 16:49 ` Jeff King
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=20130628163153.GA9127@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
/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).