On Thu, May 6, 2010 at 5:35 PM, Edward K. Ream <[email protected]> wrote:
> My question wasn't intended to start a debate about the relative > merits of various source code control systems. Rather, I want to know > whether I should be concerned, (or very very concerned) about the > stability of bzr. Frankly, I think you shouldn't. While the repo changes have caused some annoyances (with zero data loss - basically just a little extra work), bzr is still a good choice for a project the size of leo. While git is very fast, it's also very easy to screw up with it, in a way that you lose data. It also has a sucky windows implementation. Moreover, it's hard to learn, so you spend time doing vcs that you could be coding. With bzr (or hg) you just pick up the tool and get going. Git is #1 choice for huge projects like linux kernel or Qt but that's a different ballpark. -- Ville M. Vainio http://tinyurl.com/vainio -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
