From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2009, #03; Wed, 11)
Date: Wed, 11 Mar 2009 11:59:21 +0200 [thread overview]
Message-ID: <94a0d4530903110259q3db690a3leaceff4ddef2869@mail.gmail.com> (raw)
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:
> ----------------------------------------------------------------
> [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
next prev parent reply other threads:[~2009-03-11 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 9:26 What's cooking in git.git (Mar 2009, #03; Wed, 11) Junio C Hamano
2009-03-11 9:59 ` Felipe Contreras [this message]
2009-03-11 15:01 ` Jay Soffian
2009-03-11 22:37 ` Thomas Rast
2009-03-11 22:40 ` [PATCH] send-email: test --no-thread --in-reply-to combination Thomas Rast
2009-03-12 20:22 ` What's cooking in git.git (Mar 2009, #03; Wed, 11) René Scharfe
2009-03-12 20:43 ` 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=94a0d4530903110259q3db690a3leaceff4ddef2869@mail.gmail.com \
--to=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).