From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Carlos Rica <jasampler@gmail.com>,
git@vger.kernel.org, johannes.schindelin@gmx.de
Subject: Re: [PATCH] config: --replace-all with one argument exits properly with a better message.
Date: Sat, 14 Mar 2009 18:53:24 -0700 [thread overview]
Message-ID: <7vab7na6wb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <94a0d4530903141434w2fb8aa28we087465482a12e41@mail.gmail.com> (Felipe Contreras's message of "Sat, 14 Mar 2009 23:34:55 +0200")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> On Sat, Mar 14, 2009 at 10:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Carlos Rica <jasampler@gmail.com> writes:
>>
>>> 'config --replace-all ONE_ARG' was being treated as 'config NAME VALUE',
>>> showing the error "key does not contain a section: --replace-all".
>>
>> Hmm, I am getting "error: wrong number of arguments" followed by the long
>> and somewhat annoying "usage" from the parseopt table dump.
>
> If you find it annoying why don't you remove the usage?
Because the primary target audience of the help text is not me?
>> Can you work with Felipe to see if this is still needed, or needs to be
>> fixed in a different way? It could be that your tests may already pass
>> over there on 'next'. I didn't check.
>
> The new code is already checking correctly that --replace-all needs at
> least two arguments. However, the "usage" is incorrect and of course
> the test will come in handy.
So perhaps you can pick a part of it and send in an update to your
parseoptification series? I think the series is ready for 'master'
sometime next week if not sooner.
next prev parent reply other threads:[~2009-03-15 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 2:42 [PATCH] config: --replace-all with one argument exits properly with a better message Carlos Rica
2009-03-14 20:53 ` Junio C Hamano
2009-03-14 21:34 ` Felipe Contreras
2009-03-15 1:53 ` Junio C Hamano [this message]
2009-03-15 10:26 ` Felipe Contreras
2009-03-16 14:41 ` Carlos Rica
2009-03-16 15:25 ` Felipe Contreras
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=7vab7na6wb.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jasampler@gmail.com \
--cc=johannes.schindelin@gmx.de \
/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.