In November of 2012, the tmux project hosted here (tmux,sf,net) was converted over to your newer project system. Before that point, there were two Git repos. One was called "tmux", the other "tmux-openbsd". We are concerned only with the "tmux" repo.
When the project was converted over, the "tmux" repo became "code". Yet this new "code" repository is out of date at the point it was converted over. I would have hoped that this new "code" repository was a simple cp/scp of the original "tmux" repository, but this seems not to be the case.
The older "tmux" repo (which on disk is):
This bare repo has a .git/replaces/ directory which is really important. The newer "code" repo on disk, does not.
How was this "code" repository created? It can't simply have been a straight-forward "cp" or "scp". I hope you didn't simply "git clone", and expect that to work either, as parts of the metadata simply are not transferred at that point.
What I would like to see as a solution to this is the following:
/home/git/p/tmux/code.git and /home/scm_git/tmux/tmux
(It's annoying/unnecessary that the name of the repo should change, so I suggest symlinking)
3. That you review your procedure surrounding project "upgrades" because the way you've handled git migration -- is both sloppy and completely unnecessary. There is no need to change file-path locations (and in doing so breaking every git clone done in the past).
I am happy to help you with point 3,
Any questions, please ask.
-- Thomas Adam