From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Make builtin-tag.c use parse_options.
Date: Fri, 09 Nov 2007 14:57:48 +0100 [thread overview]
Message-ID: <fh1p10$nta$1@ger.gmane.org> (raw)
In-Reply-To: 473463E0.7000406@gmail.com
Carlos Rica wrote:
> + struct option options[] = {
> + { OPTION_STRING, 'l', NULL, &list, "pattern", "list tag names",
> + PARSE_OPT_OPTARG, NULL, (intptr_t) no_pattern },
> + OPT_STRING('F', NULL, &msgfile, "file", "message in a file"),
Does it matter that you use OPTION_STRING here and OPT_STRING macro there?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-11-09 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 13:42 [PATCH] Make builtin-tag.c use parse_options Carlos Rica
2007-11-09 13:57 ` Jakub Narebski [this message]
2007-11-09 14:31 ` Johannes Schindelin
2007-11-10 6:07 ` Junio C Hamano
2007-11-10 9:26 ` Junio C Hamano
2007-11-10 9:41 ` Junio C Hamano
2007-11-10 12:25 ` Carlos Rica
2007-11-10 13:13 ` Pierre Habouzit
2007-11-12 13:09 ` Carlos Rica
2007-11-12 14:52 ` Pierre Habouzit
2007-11-12 19:48 ` Kristian Høgsberg
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='fh1p10$nta$1@ger.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).