From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] completion: add missing configuration variables
Date: Wed, 15 Dec 2010 20:44:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.10.1012151931030.25560@debian> (raw)
In-Reply-To: <20101215130046.GB25647@sigill.intra.peff.net>
On Wed, 15 Dec 2010, Jeff King wrote:
> On Wed, Dec 15, 2010 at 07:46:53AM +0100, Martin von Zweigbergk wrote:
>
> > The color.grep.external option has been deleted. Should it be deleted
> > from here or do we want to help users run e.g.
> > 'git config --unset color.grep.external'? Same goes for
> > add.ignore-errors.
>
> IMHO, they should go away. People who have them can figure out how to
> delete them, but it is more important not to advertise them to people
> who are adding variables.
Sounds good to me. If no one disagrees, I'll send an updated patch in
a day or two, removing both color.grep.external and add.ignore-errors.
> As an aside, I would think "--unset" should actually choose from the set
> of configured variables for completion (i.e., "git config --list | cut
> -d= -f1"). But that would obviously be a separate patch.
Good point. I'll put it on my todo.
> > Some variables are documented with camelCase but read in all
> > lowercase in the code. Not worth updating the code just for that, is
> > it?
>
> All variables are case-insensitive.
That I knew...
> The config parser down-cases them,
> so all code should treat tham as all-lowercase.
... but not that. Thanks. I could/should have figured that out if I
had noticed that *all* of them were lowercase in the code :-P.
> One note:
>
> > color.diff
> > color.diff.commit
> > color.diff.frag
> > + color.diff.func
> > color.diff.meta
> > color.diff.new
> > color.diff.old
> > color.diff.plain
> > color.diff.whitespace
>
> We have color.diff.branch coming soon (I think it is in 'next' now).
Strictly speaking, that note is for Junio to think of when he merges,
right? But adding it early is pretty harmless and if that relieves him
of some work, I would be happy to add it in the next submission of
this patch. Is that better?
Thinking a bit more, maybe what you are suggesting is that I base the
next revision of this patch on the branch that adds that variable?
/Martin
next prev parent reply other threads:[~2010-12-16 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 6:46 [PATCH] completion: add missing configuration variables Martin von Zweigbergk
2010-12-15 13:00 ` Jeff King
2010-12-15 19:44 ` Martin von Zweigbergk [this message]
2010-12-16 4:23 ` Jeff King
2010-12-17 20:52 ` Junio C Hamano
2010-12-17 21:04 ` Jeff King
2010-12-16 12:42 ` SZEDER Gábor
2010-12-16 7:14 ` Martin von Zweigbergk
2010-12-16 14:28 ` Jeff King
2010-12-17 20:44 ` Junio C Hamano
2010-12-17 21:21 ` Jeff King
2010-12-20 15:18 ` [PATCH v2] " Martin von Zweigbergk
2010-12-20 21:20 ` Jeff King
2010-12-21 1:22 ` 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=alpine.DEB.1.10.1012151931030.25560@debian \
--to=martin.von.zweigbergk@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).