On 11/26/2012 5:30 PM, Junio C Hamano wrote:
Brandon Casey <bcasey@xxxxxxxxxx> writes:From: Brandon Casey <drafnel@xxxxxxxxx> This example in the documentation seems to be trying to describe the likely remote tracking branch that will be updated by a push to the "origin" remote with the destination branch 'satellite/master', but it forgot to specify the remote name in the path specification. So, refs/remotes/satellite/master should be spelled like refs/remotes/origin/satellite/masterI might make sense to rename 'origin' to 'mothership' in that example and explain that this is emulating 'git fetch' run on the mothership to integrate the work done on 'satellite' using 'git push' in the opposite direction, which is often necessary when you can only make connection in one way (i.e. satellite can ssh into mothership but mothership cannot initiate connection to satellite because the latter is behind a firewall or does not run sshd). If you were to run 'git fetch' on the mothership to intgrate the work on the 'satellite', it would have a remote called 'satellite', and would keep remote-tracking branches for the branches local to 'satellite' in the 'refs/remotes/satellite/' hierarchy. You would push your local 'master' to their 'refs/remotes/satellite/master', to emulate 'git fetch' done on the mothership in the reverse direction. So refs are correct. The context is not sufficiently explained.
Ah, I see. Yeah, I think that is complex enough to merit an extended explanation. -Brandon ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- -- 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