From: Jeff King <peff@peff.net>
Date: Wed, 03 Feb 2016 05:53:38 GMT
Subject: Re: [PATCH] Trick to force setup of a specific configured E-Mail per repo
Message-ID: <20160203055338.GA22818@sigill.intra.peff.net>
In-Reply-To: <CACsJy8CbnPGz40Bb+u-_QJCRT0r2p1FUQo1Ywu5F9cz+szUGtw@mail.gmail.com>

On Wed, Feb 03, 2016 at 12:26:36PM +0700, Duy Nguyen wrote:

> >> Should we generalize this use case, i.e. define a list of
> >> configuration variables that must be (re-)defined per-repo? Maybe not
> >> worth it, I don't know. I can't think of any other variable that
> >> should behave this way off the top of my head.
> >
> > That's an interesting thought, but I'm not sure how it would work. The
> > ident variables are special in that people are often unhappy with the
> > fallback. What would it mean for somebody to say "do not proceed if
> > diff.renameLimit is not set", and where would we enforce that?
> 
> Enforcing it at git-init and git-clone, interactively asking the
> values of these variables,  may be too much. If only we can catch if a
> variable is used, then we probably can catch it there. But that may
> require some more changes in config api.

Yeah, maybe. I do not want to say "definitely not", but I do think this
is sufficiently more complicated than something like user.guessIdent
that we should not make it a dependency.

-Peff