Re: Allowing override of the default "origin" nickname

Hi,

On Fri, 11 Jan 2008, Mark Levedahl wrote:

On Jan 11, 2008 8:52 AM, Johannes Schindelin [off-list ref] wrote:

quoted

IMHO you should optimise the communication by agreeing on one origin, 
or alternatively not talk about a server at all (which is made easy by 
the global uniqueness of commit names; just say "my tip is ac9b7192").

We *cannot* agree on one definition of "origin": there is no single 
server accessible by all, but use of submodules currently *requires* 
that each repo's upstream be given the nickname "origin". With this 
change, I can enforce that each server has a unique nickname and that 
one unique nickname per server is used across the program. Absent this, 
I cannot and end up having to have everyone translate "origin" into what 
it means for them.

SHA-1's are absolutely unique, but what do you do when "origin" does not 
have acdc101? I want to know that server-x@joe.com doesn't have it, 
while server-y@mary.org does. This is the frequent problem in 
conversation, and is the reason we have to be able to talk about the 
particular upstream server.

Okay, so with your change the user has to either remember or lookup which 
is the default remote.  Without your change, the user has to either 
remember or lookup where origin points to.

I still think your change does not help.

Ciao,
Dscho