git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Rica <jasampler@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: felipe.contreras@gmail.com, gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] config: test for --replace-all with one argument and fix  documentation.
Date: Tue, 17 Mar 2009 12:12:55 +0100	[thread overview]
Message-ID: <1b46aba20903170412u69041a71h3ccd97d0b61390d2@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0903171123530.6393@intel-tinevez-2-302>

On Tue, Mar 17, 2009 at 11:24 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Tue, 17 Mar 2009, Carlos Rica wrote:
>
>> Option --replace-all only allows at least two arguments, so
>> documentation was needing to be updated accordingly. A test showing
>> that the command fails with only one parameter is also provided.
>>
>> Signed-off-by: Carlos Rica <jasampler@gmail.com>
>
> Looks obviously correct to me.  I am actually unsure if I can ACK this
> patch, as most of builtin-config.c does not look all that familiar to me
> anymore ;-)

Thank you Johannes, I think that you don't need to do it in this
patch, I talked before with Junio and Felipe for this, and I think
that Junio is also following the whole change (my change here is not
comparable with the work of Felipe).

I just added you because Felipe Contreras said that you made some
suggestions to make this use of parse options possible.

See you!

      parent reply	other threads:[~2009-03-17 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  9:46 [PATCH] config: test for --replace-all with one argument and fix documentation Carlos Rica
2009-03-17 10:24 ` Johannes Schindelin
2009-03-17 10:41   ` Felipe Contreras
2009-03-17 11:02     ` Uwe Kleine-König
2009-03-17 11:12   ` Carlos Rica [this message]

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=1b46aba20903170412u69041a71h3ccd97d0b61390d2@mail.gmail.com \
    --to=jasampler@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).