Re: What's cooking in git.git (Apr 2013, #05; Mon, 15)
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:56:51
Felipe Contreras [off-list ref] writes:
So it should be clear now: the remote namespace refs/origin/master is updated, but not the remote helper's namespace refs/testgit/origin/master, which is what I already said. I don't know what more do you expect. When you push 'refs/heads/master' to origin, you expect 'refs/remotes/origin/master' to point to the same commit, same with 'refs/testgit/origin/master', why would you expect to point somewhere else?
Let me play somebody who comes later and wonders about this exchange three months down the road... You mention three refs/ here. Do they live in the same repository? Any Git person is expected to know refs/heads/master, which is "my local branch I have worked on and I am pushing". It also is easy to guess what "refs/remotes/origin/master" is, even though we are not talking about a usual Git remote. It is to keep track of the remote behind the helper we are pushing into, and is updated to pretend as if we fetched immediately from the place we just pushed. The latter being in sync with what we pushed is something that can naturally be expected. Now, what is this third "refs/testgit/origin/master" thing? Is it expected to always be the same as "refs/remotes/origin/master"? If that is the case, why do we even need such a redundant information in the first place?