Re: [PATCH 2/2] Add support for url aliases in config files

[Junio C Hamano <gitster@pobox.com>]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> So you mean
>
> [url A]
> 	standsFor = B
> 	standsFor = C
>
> ? ;-)
>
> This might be seen as bike-shedding by some, but I think that it is 
> actually worthwhile to kick back and forth some ideas, and pick the best 
> one.

It appears that Daniel and I disagree which one we should
consider canonical and which one substitute.  I tend to think
what you would see in the mailing list announce (B and C) are
canonical and you rewrite them to adjust to your local needs
(A).  But Daniel has a point that to the environment that needs
to access the repository as A, that name is the canonical one.

I am not very much interested in resolving which one is which.

In either case, I think a good approach to take is to find a
wording that conveys the notion "I will use A to mean what some
other people might call B or C" unambiguously.

When you have the above in $HOME/.gitconfig, it would mean 
"To me, A stands for B or C".  If you have it in .git/config of
the project, you are saying "When pushing/fetching in this
repository, A stands for B or C".  I think that is a reasonable
way to express what we want.