Re: What's cooking in git.git (Mar 2009, #03; Wed, 11)

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Mar 11, 2009, 09:59 UTC
Message-ID: <94a0d4530903110259q3db690a3leaceff4ddef2869@mail.gmail.com>
In-Reply-To: <7vvdqg5s17.fsf@gitster.siamese.dyndns.org>

On Wed, Mar 11, 2009 at 11:26 AM, Junio C Hamano <gitster@pobox.com> wrote:

Show 13 quoted lines

> ----------------------------------------------------------------
> [Actively cooking]
>
> * fc/parseopt-config (Sat Mar 7 12:14:05 2009 -0500) 9 commits
>  + config: set help text for --bool-or-int
>  + git config: don't allow --get-color* and variable type
>  + git config: don't allow extra arguments for -e or -l.
>  + git config: don't allow multiple variable types
>  + git config: don't allow multiple config file locations
>  + git config: reorganize to use parseopt
>  + git config: reorganize get_color*
>  + git config: trivial rename in preparation for parseopt
>  + git_config(): not having a per-repo config file is not an error

Can you answer my last email regarding this? You didn't like my last patch and explained me how the config --get-color* stuff works, and now that I understand I think the patch still makes sense.

-- 
Felipe Contreras