Björn Steinbrink <B.Steinbrink@xxxxxx> writes: > A different approach, which feels more in-line with the current state of > things, might be to allow remote aliases. "origin" would be an alias of > "myremote", and "git remote show origin" might say "origin is an alias > for myremote" followed by the details of "myremote". So that would give > you the same benefit, but "origin" would keep its meaning, and you would > not get different behaviour depending on some configuration setting (so > the poor folks on #git can just assume that "origin" is the default for > everyone). > > Admittedly, I don't see any use-case for aliases except for that origin > thing, but maybe someone else does? Aliases for remotes can address current deficiency in git, namely that you cannot have push and pull under the same remote if they use different URLs. One could use such alias to have the same name for pull and for push. -- Jakub Narebski Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
