Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config

From: Andreas Ericsson <ae@op5.se>
Date: Nov 28, 2005, 13:11 UTC
Message-ID: <438B021F.5030204@op5.se>
In-Reply-To: <200511281359.04741.Josef.Weidendorfer@gmx.de>

Josef Weidendorfer wrote:

Show 5 quoted lines

> 
> To allow for this, git_config() should not be hardcoded to only
> read .git/config, but perhaps a list of files in environment variable
> GIT_CONFIG_FILES.
>

$HOME/.gitrc:$GIT_DIR/conf/*

All files could support the freestanding "include" syntax.

Show 6 quoted lines

> For (2), git-clone should copy some files, e.g. the .git/project.conf
> or .git/info/exclude. But project config probably should be kept
> up to date among all repositories for a project, i.e. it should be
> version controlled itself, but independent from the project.
> We could use a project config head .git/refs/projectconfig for this;
> of course post-1.0 material.

It would be very nifty to have some files that can hold maintainer-like variables (like upstream email address for patches).

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231