Git Push :- Only Current Branch. Recently, when sharing a bare repository on my machine with one of the members on my team, we ran into a funny scenario.
But first, it is probably worth mentioning the following information:We are currently using git to push to svnWe have a master branch that is tracking the svn/trunk I created a new bare repository that will allow us work together on a specific task. When using Git, you only want to push into a bare repository (a repo without a working directory), instead of the real one. He was able to pull the code just fine, but when he tried to push the changes into the bare repository, not only did it try to push the branch that we were currently working on, but it also tried to push the master branch as well. That is because the bare repository that I created, had a master branch, and so did his local, and therefore it was matching on that branches name.
Mercurial vs Git; it’s all in the branches « Felipe Contreras. I have been thinking on comparing Git to other SCM’s.
I’ve analyzed several of them and so far I’ve only done the comparison with Monotone (here). Nowadays it’s pretty clear that Git is the most widely used DSCM out there, but Mercurial is the second. So, here is a comparison between Git and Mercurial. Note: I’m a long-time advocate of Git, and a contributor to the project, so I am biased (but I hope my conclusions are not).
Hg Init: a Mercurial tutorial by Joel Spolsky.