Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote: > > So far, I heard good reasons to choose hg over git, but, besides > > the > > network problems Andreas mentioned (that Siarzhuk had with git as > > well, > > though), I haven't heard anything yet that would make git a better > > choice than hg. > Actually, the best choice would seem to be bzr right now ... It has a > feature for a local repository to be bound to the central repository, > meaning that a local commit would also go directly to the central > repository. Most changes to the Haiku codebase are of that type I > think. If one then wants to work on a local branch, it is a simple > 'unbind' command, work locally, and then bind again to share the > changes. > > From a feature point of view it seems that bzr might be a good > candidate, because it efficiently mimics Subversion's repository <-> > working copy relation while also providing tools for working locally. > This IMO is a very definite characteristic of our current development > process, and one that we should keep. Agreed, bazaar doesn't look bad - the only downside I found is that it cannot track file copies, ie. the history will be lost when copying files; the copied file will just be a new file with no history. Not sure if that's really that bad, though. The rest seems to be very comparable to hg. Bye, Axel.