From: Pierre Habouzit <madcoder@debian.org>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: [proposal] make parse-options nicer wrt optional arguments (supersedes all my recent posts on the matter)
Date: Mon, 17 Dec 2007 19:23:10 +0100 [thread overview]
Message-ID: <1197915797-30679-1-git-send-email-madcoder@debian.org> (raw)
Here is a series that aims at fixing the various issues with
parse-options that were raised recently.
* preliminary patch:
[PATCH 1/7] parse-options: Make callbacks take flags instead of boolean `unset`
* teach git parse-options to allow callbacks to ignore arguments that
don't seem to be theirs, refactors:
[PATCH 2/7] parse-options: allow callbacks to ignore arguments they don't need to use.
[PATCH 3/7] parse-options: Let the integer/string cases be callbacks as well.
[PATCH 4/7] parse-options: let OPT__ABBREV ignore arguments.
* Document this (my previous proposal + Junio's squashed):
[PATCH 5/7] parse-options: Add a gitcli(5) man page.
* Implement my `{}` proposal, a sed -e s/{}/_/ will replace {} with _
as a wildcard. Contains documentation for this placeholder.
[PATCH 6/7] parse-options: have a `use default value` wildcard.
* Somehow unrelated patch, but still parse-option related (resend):
[PATCH 7/7] git-tag: fix -l switch handling regression.
This has been pushed as my ph/parseopt branch on
git://git.madism.org/git.git.
next reply other threads:[~2007-12-17 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 18:23 Pierre Habouzit [this message]
2007-12-17 18:23 ` [PATCH 1/7] parse-options: Make callbacks take flags instead of boolean `unset` Pierre Habouzit
2007-12-17 18:23 ` [PATCH 2/7] parse-options: allow callbacks to ignore arguments they don't need to use Pierre Habouzit
2007-12-17 18:23 ` [PATCH 3/7] parse-options: Let the integer/string cases be callbacks as well Pierre Habouzit
2007-12-17 18:23 ` [PATCH 4/7] parse-options: let OPT__ABBREV ignore arguments Pierre Habouzit
2007-12-17 18:23 ` [PATCH 5/7] parse-options: Add a gitcli(5) man page Pierre Habouzit
2007-12-17 18:23 ` [PATCH 6/7] parse-options: have a `use default value` wildcard Pierre Habouzit
2007-12-17 18:23 ` [PATCH 7/7] git-tag: fix -l switch handling regression Pierre Habouzit
2007-12-17 18:56 ` Pierre Habouzit
2007-12-17 19:03 ` Pierre Habouzit
2007-12-17 20:13 ` Junio C Hamano
2007-12-18 2:00 ` [PATCH 5/7] parse-options: Add a gitcli(5) man page Wayne Davison
2007-12-17 18:54 ` [PATCH 1/7] parse-options: Make callbacks take flags instead of boolean `unset` 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=1197915797-30679-1-git-send-email-madcoder@debian.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.