From: Johannes Schindelin Date: Mon, 21 Nov 2005 15:57:07 GMT Subject: Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Message-ID: In-Reply-To: <200511211644.16789.Josef.Weidendorfer@gmx.de> Hi, On Mon, 21 Nov 2005, Josef Weidendorfer wrote: > On Monday 21 November 2005 14:56, Johannes Schindelin wrote: > > With this patch, git automatically extracts the information from > > .git/branches and .git/remotes, puts it into .git/config, and renames the > > directories to .git/branches.old and .git/remotes.old, respectively. > > Please... don't trash .git/branches. > This is about Cogito, not about Git. You will render every repository cloned > with Cogito useless, as it expects a per-branch configuration with the same > name as heads. > > The part about .git/branches has to be sent to Pasky, not Junio. I was aware that .git/branches was introduced by Pasky, but as it is handled in git-parse-remote.sh, I thought that it may be a bit more general than just cogito. Anyways, I sent this out as an *RFC*, but the "C" obviously stands for "Comments"... What do people say? Is it useless to move that information into the config, where it can be queried/replaced/set/removed by the config "API", or should we continue with two incompatible ad-hoc formats? (If that sounds biased, it was not meant to be.) Ciao, Dscho