Re: Allowing override of the default "origin" nickname

Hi,

On Thu, 10 Jan 2008, Mark Levedahl wrote:

git's current support for remote nicknames other than
"origin" is restricted to tracking branches where
branch.<name>.remote is defined.

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