Michael Olson <[EMAIL PROTECTED]> writes: > What do people think of the idea of trying out git for developing > DVC?
I can go either way. I'm not very happy with the way bzr operates; I often get confused about what just happened, or find it difficult to predict what will happen next. As long as DVC supports the operations needed, it should not be hard switching to git. It would be a good test of DVC. It would also be good to get more exposure to another distributed version control system. > I've set up a sample repo at > <git://git.hcoop.net/git/mwolson/emacs/dvc.git>. A gitweb interface is > at <http://git.hcoop.net/?p=mwolson/emacs/dvc.git;a=summary>. > > Reasons that I prefer git over bzr: > > - Merges look terrible in the bzr log output. What's up with the > indentation and the redundant listing of commits that are in the > merge? That's what DVC is for :). I don't often read logs, but I find the DVC presentation adequate. I don't recall wondering about merges. I only use bzr for DVC maintenance. Hmm. In one sense, everything in bzr is a "merge", because every developer has their own branch. That's part of my confusion. I prefer a system where everyone shares the same branch, via some sync mechanism. Monotone has that; I believe git does also. > - Git is still significantly faster for almost every operation. Since DVC is a very small project, this is not a very significant issue. -- -- Stephe _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
