From: Michele Ballabio <barra_cuda@katamail.com>
To: git@vger.kernel.org
Cc: Stephan Beyer <s-beyer@gmx.net>,
Pierre Habouzit <madcoder@debian.org>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/2] api-parse-options.txt: Introduce documentation for parse options API
Date: Sun, 22 Jun 2008 14:49:08 +0200 [thread overview]
Message-ID: <200806221449.08307.barra_cuda@katamail.com> (raw)
In-Reply-To: <1214092802-8175-1-git-send-email-s-beyer@gmx.net>
On Sunday 22 June 2008, Stephan Beyer wrote:
> +`PARSE_OPT_KEEP_DASHDASH`::
> + Usually long options (`\--long-opt`) are boiled down to their
> + short option equivalent, if available.
> + Using this flag, long options are kept.
No: PARSE_OPT_KEEP_DASHDASH keeps the "--" that usually separates options
from files, as in
git ls-files [options] -- [files]
i.e. after parsing, the new argv will still contain "--".
> +`OPT__ABBREV(&int_var)`::
> + Add `\--abbrev [<n>]`.
better:
+ Add `\--abbrev[=<n>]`.
since the <n> is optional.
next prev parent reply other threads:[~2008-06-22 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 0:00 [PATCH 1/2] api-parse-options.txt: Introduce documentation for parse options API Stephan Beyer
2008-06-22 0:00 ` [PATCH 2/2] Extend parse-options test suite Stephan Beyer
2008-06-22 12:49 ` Michele Ballabio [this message]
2008-06-22 13:45 ` [PATCH 1/2] api-parse-options.txt: Introduce documentation for parse options API Stephan Beyer
2008-06-22 14:39 ` [PATCH] parse-options.c: fix documentation syntax of optional arguments Michele Ballabio
2008-06-22 15:04 ` [PATCH v2 1/2] api-parse-options.txt: Introduce documentation for parse options API Stephan Beyer
2008-06-22 15:04 ` [PATCH v2 2/2] Extend parse-options test suite Stephan Beyer
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=200806221449.08307.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=madcoder@debian.org \
--cc=s-beyer@gmx.net \
/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).