From: Jacob Keller <jacob.e.keller@intel.com>
To: git@vger.kernel.org
Cc: Jacob Keller <jacob.keller@gmail.com>
Subject: [PATCH 1/5] doc: add documentation for OPT_STRING_LIST
Date: Wed, 11 Jan 2017 16:17:17 -0800 [thread overview]
Message-ID: <20170112001721.2534-2-jacob.e.keller@intel.com> (raw)
In-Reply-To: <20170112001721.2534-1-jacob.e.keller@intel.com>
From: Jacob Keller <jacob.keller@gmail.com>
Commit c8ba16391655 ("parse-options: add OPT_STRING_LIST helper",
2011-06-09) added the OPT_STRING_LIST as a way to accumulate a repeated
list of strings. However, this was not documented in the
api-parse-options documentation. Add documentation now so that future
developers may learn of its existence.
Signed-off-by: Jacob Keller <jacob.keller@gmail.com>
---
Documentation/technical/api-parse-options.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/technical/api-parse-options.txt b/Documentation/technical/api-parse-options.txt
index 27bd701c0d68..15e876e4c804 100644
--- a/Documentation/technical/api-parse-options.txt
+++ b/Documentation/technical/api-parse-options.txt
@@ -168,6 +168,11 @@ There are some macros to easily define options:
Introduce an option with string argument.
The string argument is put into `str_var`.
+`OPT_STRING_LIST(short, long, &list, arg_str, description)`::
+ Introduce an option with a string argument. Repeated invocations
+ accumulate into a list of strings. Reset and clear the list with
+ `--no-option`.
+
`OPT_INTEGER(short, long, &int_var, description)`::
Introduce an option with integer argument.
The integer is put into `int_var`.
--
2.11.0.403.g196674b8396b
next prev parent reply other threads:[~2017-01-12 0:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 0:17 [PATCH 0/5] extend git-describe pattern matching Jacob Keller
2017-01-12 0:17 ` Jacob Keller [this message]
2017-01-12 9:47 ` [PATCH 1/5] doc: add documentation for OPT_STRING_LIST Johannes Schindelin
2017-01-13 0:51 ` Jacob Keller
2017-01-12 0:17 ` [PATCH 2/5] name-rev: extend --refs to accept multiple patterns Jacob Keller
2017-01-12 9:56 ` Johannes Schindelin
2017-01-13 0:56 ` Jacob Keller
2017-01-12 0:17 ` [PATCH 3/5] name-rev: add support to discard refs by pattern match Jacob Keller
2017-01-12 9:57 ` Johannes Schindelin
2017-01-13 0:56 ` Jacob Keller
2017-01-12 0:17 ` [PATCH 4/5] describe: teach --match to accept multiple patterns Jacob Keller
2017-01-12 0:17 ` [PATCH 5/5] describe: teach describe negative pattern matches Jacob Keller
2017-01-12 9:42 ` Johannes Schindelin
2017-01-12 22:02 ` Junio C Hamano
2017-01-12 13:45 ` Johannes Sixt
2017-01-13 0:59 ` Jacob Keller
2017-01-13 6:43 ` Johannes Sixt
2017-01-13 6:57 ` Jacob Keller
2017-01-13 21:31 ` Johannes Sixt
2017-01-17 23:31 ` Jacob Keller
2017-01-18 12:44 ` Johannes Schindelin
2017-01-18 21:04 ` Jacob Keller
2017-01-12 10:05 ` [PATCH 0/5] extend git-describe pattern matching Johannes Schindelin
2017-01-13 18:48 ` Junio C Hamano
2017-01-13 20:41 ` Jacob Keller
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=20170112001721.2534-2-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--cc=git@vger.kernel.org \
--cc=jacob.keller@gmail.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).