From: Junio C Hamano <gitster@pobox.com>
To: Pierre Habouzit <madcoder@debian.org>
Cc: git@vger.kernel.org
Subject: [PATCH/RFC] parse-options: allow to define hidden synonym options
Date: Sun, 18 Nov 2007 22:09:41 -0800 [thread overview]
Message-ID: <7v4pfircka.fsf@gitster.siamese.dyndns.org> (raw)
By setting the help member to NULL, you can implement an option
that is not shown in the "git-cmd -h" help output. This is
useful to support backward compatible synonyms without
cluttering the help text.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
parse-options.c | 2 ++
parse-options.h | 2 +-
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/parse-options.c b/parse-options.c
index d3e608a..1ee2c81 100644
--- a/parse-options.c
+++ b/parse-options.c
@@ -284,6 +284,8 @@ void usage_with_options(const char * const *usagestr,
if (*opts->help)
fprintf(stderr, "%s\n", opts->help);
continue;
+ } else if (!opts->help) {
+ continue;
}
pos = fprintf(stderr, " ");
diff --git a/parse-options.h b/parse-options.h
index a8760ac..de249a0 100644
--- a/parse-options.h
+++ b/parse-options.h
@@ -49,7 +49,7 @@ typedef int parse_opt_cb(const struct option *, const char *arg, int unset);
*
* `help`::
* the short help associated to what the option does.
- * Must never be NULL (except for OPTION_END).
+ * option with this field set to NULL does not appear in the help listing.
* OPTION_GROUP uses this pointer to store the group header.
*
* `flags`::
--
1.5.3.6.1779.ga3ed
next reply other threads:[~2007-11-19 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 6:09 Junio C Hamano [this message]
2007-11-19 8:04 ` [PATCH Illustration] branch --contains=<commit> Junio C Hamano
2007-11-19 9:22 ` [PATCH/RFC] parse-options: allow to define hidden synonym options 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=7v4pfircka.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.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).