Re: Setting per-repository configuration for git

From: Jakub Narebski <jnareb@gmail.com>
Date: Oct 25, 2013, 12:37 UTC
Message-ID: <loom.20131025T143218-801@post.gmane.org>
In-Reply-To: <20131025082513.GE17029@sigill.intra.peff.net>

Jeff King <peff <at> peff.net> writes:

Show 6 quoted lines

> On Fri, Oct 25, 2013 at 09:12:35AM +0200, Jeremy Rosen wrote:
> 
> > however I can't find a way to have the repository's configuration 
> > saved and transmited with the repository in a way similar to how
> > .gitignore is transmitted...
> > [...]

Show 7 quoted lines

> Two, the config is not really tied to a specific revision in the same
> way that a .gitignore is. If I move to another branch, or checkout an
> old revision, I would want to use the .gitignore from the currently
> checked-out commit. But git config does not typically work that way. If
> I am sight-seeing back to last year's history, I do not want to use a
> different remote URL, or different diff settings, etc. So managing a
> .gitconfig directly in the repository has some ugly edge cases.

Nb. *Mercurial* uses in repository .hgtags file for shared tags (instead of using separate transport mechanism, like Git does with refs, of which tags are special case). Said file has to be treated in a special way, with some sharp corner-cases (e.g. committing a tag (sic!)).

-- 
Jakub Narębski