Re: [RFC] control, what refs are honored by core.logAllRefUpdates

From: Jeff King <peff@peff.net>
Date: Jul 13, 2011, 08:59 UTC
Message-ID: <20110713085915.GA29900@sigill.intra.peff.net>
In-Reply-To: <CAKPyHN1GEkcyacQ_f4hhjaaZx4Fx4tmfz0qRSfTPXJDgUm8mow@mail.gmail.com>

On Wed, Jul 13, 2011 at 10:52:58AM +0200, Bert Wesarg wrote:

Show 16 quoted lines

> On Tue, Jul 12, 2011 at 20:25, Jeff King <peff@peff.net> wrote:
>  [1] If we were starting from scratch, you could make that distinction
> > with a new operator, like:
> >
> >  [core]
> >    autoLogRef = heads
> >    autoLogRef += remotes
> >    autoLogRef += notes
> >    autoLogRef = heads
> >
> > which would be equivalent to what you wrote above. But because it
> > switches the semantics of "=" to "replace" instead of "append" for
> > multi-value keys, it would break all current config that uses multiple
> > "fetch" lines (for example).
> 
> Adding ! as a negator would also break config files read by old git versions.

True. I consider that less bad than "existing config files are broken", but it is still worth thinking about. It really only affects people who move back and forth between git versions using the same set of config files.

In general, our config stays pretty compatible between versions, but there are exceptions. E.g., older versions of git will complain about:

  [pager]
    log = whatever

because "pager.*" previously had to be a bool. I run into this when testing old git versions.

I have no idea how common that sort of thing is with regular users, though.

-Peff