Re: [PATCH 3/3] fetch: optionally store the current remote information in the config

Hi,

On Sun, 30 Apr 2006, sean wrote:

On Sun, 30 Apr 2006 17:49:06 +0200 (CEST)
Johannes Schindelin [off-list ref] wrote:

quoted

The latter should be done, because "git fetch" really is about fetching, 
not playing games with the config.

Then we should also remove the --store option from pull and fetch.  It
can be set with git-repo-config.

Well, with "--store", "git fetch" still fetches. It just happens to write 
down -- for convenience -- the possibly long url and the refspecs.

quoted

FETCH_HEAD can contain multiple refs. 

Which head does git-pull then use to merge, all of them?

The first one.

quoted

And I don't get the part about fetching from multiple remotes: 
my patch does not allow for that.

Actually it does :o)  User just needs multiple remote.$nick.url entries 
in his config.

You are right. But you are also wrong. The patch uses

	git-repo-config --get remote.$nick.url

which fails if there are more than one matching line. Note that 
"--get-all" is used to get _all_ remote.$nick.pull lines...

But of course, Linus "built git-push in" so that multiple urls are 
allowed and handled. It is probably confusing, if you can push but 
cannot fetch with the same remote information... But then, I fail to see 
how you could possibly specify the refspecs for the different urls.

Ciao,
Dscho