Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bernhard Reiter <ockham@raz.or.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] imap-send: Use parse options API to determine verbosity
Date: Wed, 05 Nov 2014 16:01:11 -0800	[thread overview]
Message-ID: <xmqqbnoli4e0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <545AAA60.3040207@raz.or.at> (Bernhard Reiter's message of "Wed, 05 Nov 2014 23:53:20 +0100")

Bernhard Reiter <ockham@raz.or.at> writes:

> Signed-off-by: Bernhard Reiter <ockham@raz.or.at>
> ---
> In reply to <xmqqk339ibal.fsf@gitster.dls.corp.google.com>.
>
> Thanks for bearing with me. I should've given the corresponding verbosity
> values more thought myself in the first place.

The original defined and even used these two variables, but as far
as I can tell they were always set to 0 and nobody modified them.
Hence, we would be OK as long as the end result will behave the same
as before without any -v/-q from the command line ;-)

Thanks.  This version looks more sensible.

> -	if (argc != 1)
> -		usage(imap_send_usage);
> -
>  	setup_git_directory_gently(&nongit_ok);
>  	git_imap_config();
>  
> +	argc = parse_options(argc, (const char **)argv, "", imap_send_options, imap_send_usage, 0);
> +

... except we might want to check argc here and say something about
missing or excess parameters, which was lost in the change in this
hunk.  I think (without giving it a real thought, though ;-) you
would expect that nothing remains on the command line after
parse_options() has done its thing, no?


>  	if (!server.port)
>  		server.port = server.use_ssl ? 993 : 143;

  reply	other threads:[~2014-11-06  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 22:53 [PATCH v2] imap-send: Use parse options API to determine verbosity Bernhard Reiter
2014-11-06  0:01 ` Junio C Hamano [this message]
2014-11-06  0:30   ` Junio C Hamano

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=xmqqbnoli4e0.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ockham@raz.or.at \
    /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