Git development
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC] ignore unknown color configuration
Date: Tue, 15 Dec 2009 22:45:29 -0500	[thread overview]
Message-ID: <20091216034529.GA9742@sigill.intra.peff.net> (raw)
In-Reply-To: <7v3a3bwvzj.fsf@alter.siamese.dyndns.org>

On Tue, Dec 15, 2009 at 05:25:36PM -0800, Junio C Hamano wrote:

> >> I would be more sympathetic to that user if this weren't the _only_ set
> >> of variables with this property. They don't get warned for diff.externel
> >> or color.show-branch.
> >
> > True and fair enough.  Let's have this in 1.6.6 then.
> 
> Actually I think we should have this in 1.6.5.X as well for it to be
> useful.  Am I mistaken?

The earlier the better for making it useful, but it is still somewhat of
a lost cause for color.diff.func. The problem comes from using git
v1.6.6, setting the variable, and then going to back to some older
version (either because you are testing multiple versions, or because
your config is shared across multiple machines).

So yes, putting it in v1.6.5.x means switching back there will not be as
painful. But switching back to existing versions will still be broken
until all older versions you might want to switch to have this patch.

So we are not so much fixing this color.diff.func problem as
future-proofing against this happening again.

-Peff

  reply	other threads:[~2009-12-16  3:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12 12:25 [PATCH/RFC] ignore unknown color configuration Jeff King
2009-12-12 21:45 ` Junio C Hamano
2009-12-12 22:20   ` Jeff King
2009-12-14  2:33     ` Junio C Hamano
2009-12-16  1:25       ` Junio C Hamano
2009-12-16  3:45         ` Jeff King [this message]
2009-12-16  1:29 ` Junio C Hamano
2009-12-16  3:46   ` Jeff King

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=20091216034529.GA9742@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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