I want a network filesystem that continues to work when the network goes away, and magically reconciles stuff when it comes back. (For use on a Linux laptop which mostly lives in a docking station, but not always
( Read more... )
Any specific reasons? (Having done a bit more reading, the "renames are explicitly tracked not inferred" feature of bazaar seems less of an advantage than it did when I was first Googling, and "git is more popular" is probably enough.)
My experience of bzr is from a few years ago and it was a bit ropey in basic places (bzrignore comes to mind).. alas I don't have any more than that.
Git and its tools are lightning fast, having been designed to cope with the kernel source tree. hg is OK but sometimes chugs a bit, particularly with large repos (work has around 58k commits), and tortoisehg can be slow at times because of this.
A few years ago, at a previous employer, hg and git were the two front runners in the race, considered about equally powerful - the choice came down to the windows tools being better for hg at that time, though I gather that git may have caught up a bit.
Comments 4
Reply
Reply
Git and its tools are lightning fast, having been designed to cope with the kernel source tree. hg is OK but sometimes chugs a bit, particularly with large repos (work has around 58k commits), and tortoisehg can be slow at times because of this.
A few years ago, at a previous employer, hg and git were the two front runners in the race, considered about equally powerful - the choice came down to the windows tools being better for hg at that time, though I gather that git may have caught up a bit.
Reply
Reply
Leave a comment