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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 11, 2009 at 11:26 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote:
> ----------------------------------------------------------------
> [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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux