Finn Arne Gangstad <finnag@xxxxxxx> writes:
> The main problem with all these examples is that the underlying
> assumption is that you can always use the same branch name locally and
> remotely.
Presumably the push --track option would be used with an explicit branch
name given to push anyway, right? Then it can use that info to set up
the tracking flexibly (and with sane defaults).
E.g.,, simple case:
git push --track SOME_REMOTE BRANCH_NAME
complex case:
git push --track SOME_REMOTE MY-BRANCH:REMOTE-BRANCH
-Miles
--
=====
(^o^;
(()))
*This is the cute octopus virus, please copy it into your sig so it can spread.
--
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
