From: Jakub Narebski <jnareb@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] config: Use parseopt.
Date: Sat, 14 Feb 2009 03:52:56 -0800 (PST) [thread overview]
Message-ID: <m3skmhteuk.fsf@localhost.localdomain> (raw)
In-Reply-To: <1234577142-22965-1-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> Reorganizing the code to use parseopt as suggested by Johannes
> Schindelin.
[...]
> -static const char git_config_set_usage[] =
> -"git config [ --global | --system | [ -f | --file ] config-file ] [ --bool | --int | --bool-or-int ] [ -z | --null ] [--get | --get-all | --get-regexp | --replace-all | --add | --unset | --unset-all] name [value [value_regex]] | --rename-section old_name new_name | --remove-section name | --list | --get-color var [default] | --get-colorbool name [stdout-is-tty] | --edit | -e ]";
> +static const char *const builtin_config_usage[] = {
> + "git config [options]",
> + NULL
> +};
Just asking: why this change?
> + OPT_BOOLEAN('z', "null", &end_null, "end values with null character"),
Terminate and NUL.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-02-14 11:54 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 2:05 [PATCH] config: Use parseopt Felipe Contreras
2009-02-14 9:28 ` Junio C Hamano
2009-02-14 9:35 ` Junio C Hamano
2009-02-14 10:41 ` Felipe Contreras
2009-02-14 10:37 ` Felipe Contreras
2009-02-14 11:40 ` Johannes Schindelin
2009-02-14 12:03 ` [PATCH v2] " Felipe Contreras
2009-02-14 15:21 ` Jeff King
2009-02-14 15:24 ` Felipe Contreras
2009-02-14 19:59 ` Johannes Schindelin
2009-02-14 20:19 ` Junio C Hamano
2009-02-14 21:08 ` human readable diffs, was " Johannes Schindelin
2009-02-14 20:31 ` Felipe Contreras
2009-02-14 22:32 ` Johannes Schindelin
2009-02-14 22:36 ` Jakub Narebski
2009-02-14 22:54 ` Johannes Schindelin
2009-02-15 9:04 ` Felipe Contreras
2009-02-15 11:26 ` Johannes Schindelin
2009-02-15 12:07 ` Felipe Contreras
2009-02-15 12:33 ` Johannes Schindelin
2009-02-15 12:51 ` Felipe Contreras
2009-02-15 13:38 ` Felipe Contreras
2009-02-15 19:31 ` Junio C Hamano
2009-02-15 19:41 ` Johannes Schindelin
2009-02-15 21:22 ` Junio C Hamano
2009-02-15 21:29 ` Johannes Schindelin
2009-02-17 0:50 ` Felipe Contreras
2009-02-15 19:36 ` Junio C Hamano
2009-02-14 12:15 ` [PATCH] " Felipe Contreras
2009-02-14 19:11 ` Johannes Schindelin
2009-02-14 19:14 ` Felipe Contreras
2009-02-14 19:24 ` Johannes Schindelin
2009-02-14 19:26 ` Johannes Schindelin
2009-02-14 21:13 ` Felipe Contreras
2009-02-14 19:29 ` Junio C Hamano
2009-02-14 20:09 ` Felipe Contreras
2009-02-14 20:35 ` Junio C Hamano
2009-02-14 21:01 ` Felipe Contreras
2009-02-14 21:10 ` Junio C Hamano
2009-02-14 21:24 ` Felipe Contreras
2009-02-14 21:15 ` Johannes Schindelin
2009-02-15 2:22 ` Junio C Hamano
2009-02-14 11:52 ` Jakub Narebski [this message]
2009-02-14 12:06 ` Felipe Contreras
2009-02-14 15:17 ` Jeff King
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=m3skmhteuk.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=felipe.contreras@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).