From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sun, 30 Apr 2006 15:52:07 GMT
Subject: Re: [PATCH 3/3] fetch: optionally store the current remote information in the config
Message-ID: <Pine.LNX.4.63.0604301749130.3641@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <e32h0o$15n$1@sea.gmane.org>

Hi,

On Sun, 30 Apr 2006, Jakub Narebski wrote:

> There was thread about storing somewhere default branch we merge to during
> pull, instead of using always surrent one. Different schemes were proposed,
> most of them depending on the remotes configuration being available [also]
> in config file.

I was not following that thread closely, since it became too confusing for 
me. However, I think that my patch could be a start in that direction.

> By the way: it would be nice to have command/script to trasform freely
> between 'remotes/' and config file.

If you set the environment variable GIT_REWRITE_REMOTES to "true", and 
call git-parse-remotes.sh, it will do the rewriting to the config file. 
Obviously, I did not test that part of the patch all that well.

> P.S. I wonder if it would be difficult to implement 'include <file>' for
> config file...

You really need that?

Ciao,
Dscho