Sorry, I managed to activate some button on Google Groups accidentally and prematurely post the above message...
+100. Our main problem with Mercurial is that we are not *using* it. We are just using Mercurial as a way for Jeroen to generate changelogs, and no other collaborative purpose whatsoever (despite what individual developers such as William might be doing with qfinishing patches, committing, etc. locally). We currently get zero benefit from using a distributed version control system. I completely agree with Jason's assessment of git vs. Mercurial, namely that both are serviceable, though git is more so (due to its topic branches support). But either git or a "real" Mercurial workflow would be vastly superior to the frankly nonsensical way we're using Mercurial right now. My $0.02. Jason: I'm sure you know this, but the record extension in mercurial allows you to do the equivalent of git commit -p, and you can of course use mq with a single patch in a patch queue as a simulation of a staging area, though this is a little painful compared to git's index. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
