Re: How to use git attributes to configure server-side checks?

From: Jakub Narebski <jnareb@gmail.com>
Date: Sep 26, 2011, 14:14 UTC
Message-ID: <201109261614.09315.jnareb@gmail.com>
In-Reply-To: <20110926110552.GA20796@sigill.intra.peff.net>

Jeff King wrote:

> On Sat, Sep 24, 2011 at 01:03:50PM +0200, Michael Haggerty wrote:

Show 17 quoted lines

> > While we are on the topic of config settings, I have often thought that
> > it would be nice for git's default settings to be set via a
> > well-commented config file, installed along with git, rather than via
> > values compiled into the code.  This file and Documentation/config.txt
> > could be generated from a single source file as part of the build
> > process.
> 
> I think that can be a nice piece of documentation, but there may be some
> complications.  I seem to recall that there may be one or two options
> whose builtin values cannot be replicated via config (i.e., the "unset"
> state means something). But I may be misremembering.
> 
> However, I'm not sure what you mean by "rather than via values compiled
> into the code".  Would you somehow generate code that sets the default
> according to your master file? Would git fail to start if the file is
> missing? Or if a specific config option is missing? How would you track
> that?

There is also problem that it would screw up Git deprecation policy.
 * new behavior is introduced, with a knob that defaults to off
 * after some time knob starts to default to on
 * git uses new feature by default

With Git creating config file with state of config variables frozen at the state of repository creation this would be not possible.

-- 
Jakub Narebski
Poland