From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Git Mailing List <git@vger.kernel.org>
Cc: Pierre Habouzit <madcoder@debian.org>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/5] grep parseopt conversion
Date: Thu, 07 May 2009 21:43:00 +0200 [thread overview]
Message-ID: <1241725380.4772.6.camel@ubuntu.ubuntu-domain> (raw)
This series converts git-grep to parseopt. The first three patches
extend the parser to accept inverse bit options, numerical options
and options without dashes:
[PATCH 1/5] parseopt: add OPT_NEGBIT
[PATCH 2/5] parseopt: add OPT_NUMBER_CALLBACK
[PATCH 3/5] parseopt: add PARSE_OPT_NODASH
The fourth patch is a cleanup:
[PATCH 4/5] grep: remove global variable builtin_grep
The last patch uses the added infrastructure in git-grep:
[PATCH 5/5] grep: use parseopt
Documentation/technical/api-parse-options.txt | 12 +
builtin-grep.c | 416 +++++++++++--------------
grep.h | 28 +-
parse-options.c | 63 ++++-
parse-options.h | 14 +-
t/t0040-parse-options.sh | 56 ++++-
test-parse-options.c | 11 +
7 files changed, 348 insertions(+), 252 deletions(-)
next reply other threads:[~2009-05-07 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 19:43 René Scharfe [this message]
2009-05-07 19:44 ` [PATCH 1/5] parseopt: add OPT_NEGBIT René Scharfe
2009-05-08 5:01 ` Jeff King
2009-05-07 19:45 ` [PATCH 2/5] parseopt: add OPT_NUMBER_CALLBACK René Scharfe
2009-05-07 19:45 ` [PATCH 3/5] parseopt: add PARSE_OPT_NODASH René Scharfe
2009-05-07 19:46 ` [PATCH 4/5] grep: remove global variable builtin_grep René Scharfe
2009-05-07 19:46 ` [PATCH 5/5] grep: use parseopt René Scharfe
2009-05-16 9:44 ` Stephen Boyd
2009-05-17 19:45 ` René Scharfe
2009-05-20 22:05 ` [PATCH] grep: make callback functions static René Scharfe
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=1241725380.4772.6.camel@ubuntu.ubuntu-domain \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).