thout additional configuration, pushes the current branch to the
configured upstream (remote.origin.merge configuration variable) if it
has the same name as the current branch, and errors out without
pushing otherwise.
Thanks,
Prem
On Wed, Jan 28, 2015 at 3:37 AM, Eric Sunshine wrote:
>
I am using git 2.2.2 and want to report an issue with git push --repo option.
git 2.2.2 manual says that git push --repo=public will push to public
only if the current branch does not track a remote branch. See
http://git-scm.com/docs/git-push
However, I see that git pushes even when the current
ch to blah repository.
5. But per git manual, it shouldn't push to blah, as the local branch
is tracking "origin/whoa".
Appreciate your help.
Prem
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
3 matches
Mail list logo