Re: [PATCH] Teach remote machinery about remotes.default config variable

Hi,

On Sat, 12 Jan 2008, Mark Levedahl wrote:

Johannes Schindelin wrote:

quoted

No, that was not _at all_ my argument.

I said that hiding it under a different name _that you have to look 
up, too_ does _not_ make things easier.

  

Granted, *IF* we had to look it up, but we don't. In fact, we use the 
convention
   servername.foo.bar
has nickname
   servername

So, we need to know the server name we are using, and that server name 
is the nickname. So, no confusion and no extra lookup step. (Our server 
names are unique without the domain suffixes, so this works well for 
us).

How do you know _which_ default remote name your current repository uses? 
Exactly: you have to look it up.  So your whole *IF* argument is bogus.

And if you already have to look something up, and the user fiddled with 
her setup, you can no longer be sure that nickname servername points to 
servername.foo.bar, and you are in even more trouble.

That is why I maintain that your solution does not make things better.

Hth,
Dscho