Re: git push --repo option not working as described in git manual.
The conclusions from the last time we discussed this [*1*], the last word was that git push $some_opt... --repo=$Repo $more_opt... $args... is designed to work exactly like git push $some_opt... $more_opt... $Repo $args... and the documentation that says otherwise is incorrect. It seems that we never followed up on this after we made that determination, which is unfortunate. We should at least correct the documentation. [Reference] *1* http://thread.gmane.org/gmane.comp.version-control.git/110827/focus=111715 -- 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
git push --repo option not working as described in git manual.
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 branch is tracking a remote branch. Here is the test case (push default setting is simple, git version 2.2.2, Mac OS X 10.10.1): 1. I have a local branch "master". 2. "master" tracks remote branch "blah/master". Here "blah" is the remote repository. 3. While I am on my local master branch, I run git push --repo=silver 4. git pushes the local master branch to silver repository. 5. But per git manual, it shouldn't push to silver, as the local branch is tracking "blah/master". So is this broken or am I missing something? Here is another test case (push default setting is simple, git version 2.2.2, Mac OS X 10.10.1): 1. I have a local branch "whoa". 2. "whoa" tracks remote branch "origin/whoa". Here "origin" is the remote repository. 3. While I am on my local whoa branch, I run git push --repo=blah 4. git pushes the local whoa branch to blah repository. 5. But per git manual, it shouldn't push to blah, as the local branch is tracking "origin/whoa". So is this broken or am I missing something? Appreciate your help. -- 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
git push --repo option not working as described in git manual.
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 branch is tracking a remote branch. Here is the test case (push default setting is simple, git version 2.2.2, Mac OS X 10.10.1): 1. I have a local branch "master". 2. "master" tracks remote branch "blah/master". Here "blah" is the remote repository. 3. While I am on my local master branch, I run git push --repo=silver 4. git pushes the local master branch to silver repository. 5. But per git manual, it shouldn't push to silver, as the local branch is tracking "blah/master". Here is another test case (push default setting is simple, git version 2.2.2, Mac OS X 10.10.1): 1. I have a local branch "whoa". 2. "whoa" tracks remote branch "origin/whoa". Here "origin" is the remote repository. 3. While I am on my local whoa branch, I run git push --repo=blah 4. git pushes the local whoa branch 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
