| ▲ | bluGill 11 hours ago | |||||||
Coming from mercurial (which is older than git), git doesn't understand a branch. Instead of a branch you get a tag that moves, which is very different. Too often I'm trying to figure out where something came in, and but there is just a series of commits with no information of which commits are related. Git then developed the squash+rebase workflow which softof gets around this, but it makes commit longer (bad), and loses the real history of what happened. Git was not the first DVCS, there were better ones even when it was made. But Linus pushed git and people followed like sheep. (I'm using git, both because everyone else is, and also because github exists - turns out nobody even wants a DVCS, they want a central version control system with the warts of SVN fixed). | ||||||||
| ▲ | jcranmer 10 hours ago | parent | next [-] | |||||||
> Coming from mercurial (which is older than git) Git is older than mercurial by 12 days. Bazaar has git beat by about the same amount of time. The major DVCSes all came out within a month of each other. > But Linus pushed git and people followed like sheep. I don't think this is true. Until around 2010-2011 or so, projects moving to DVCS seemed to pick up not git but mercurial. The main impetus I think was not Linux choosing git but the collapse of alternate code hosting places other than GitHub, which essentially forced git. | ||||||||
| ||||||||
| ▲ | em-bee 10 hours ago | parent | prev [-] | |||||||
the lack of a proper branch history is also the main pain point for me. but i disagree that noone wants a DCVS. having a full copy of the history locally, and being able to clone from any repo to anywhere else and even merge repos (without merging branches) is a major win for me. | ||||||||