Re: Allowing override of the default "origin" nickname

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

Hi,

IIUC your patch only replaces the term "origin" by something
user-specifiable.  I fail to see the use of it; care to explain what
workflow is easier with your patches than without?

Ciao,
Dscho

Consider a project with several servers, each of which is *supposed*
is host the same project but due to lags in mirroring across airgaps,
etc., are never quite in sync. Now, we get on a teleconference and
discuss issues, find differences, and everyone reports that "origin"
has x, but in fact "origin" means different servers to almost
everyone. Also consider that only a small subset of the group really
understands git, most just follow cook-book recipes to get their work
done and don't understand what is going on.

This is my problem: "origin" is an abstraction that hides the
different server names in use and makes communication difficult,
having everyone use nicknames related to their particular upstream
server reduces the confusion.

Mark