From: Petr Baudis Date: Mon, 28 Nov 2005 13:48:08 GMT Subject: Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Message-ID: <20051128134808.GQ22159@pasky.or.cz> In-Reply-To: <200511281359.04741.Josef.Weidendorfer@gmx.de> Dear diary, on Mon, Nov 28, 2005 at 01:59:04PM CET, I got a letter where Josef Weidendorfer said that... > (2) project config (in .git/project.conf) What are you going to keep in it? There isn't much of stuff which is not per-user or per-instance. I can't think of anything now, but there is no list of configuration variables to check yet. (Upstream maintainer email is interesting, OTOH it alone doesn't seem to justify the mechanism by itself; also, the upstreams may be different based on where you cloned the project from, etc.) > 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. If you still want per-project config, why should it be independent from the project? Actually, like you have .gitignore, having something like .gitconfig in project root would be by far the simplest - if you want separate head, your merging and stuff gets quite more complicated, as well as actually branching the project config, etc. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ VI has two modes: the one in which it beeps and the one in which it doesn't.