![]() ![]() Let us know if you have one to add to the list. The following are configuration instructions for specific products. 注意用以版本比较时,都是使用的 bcomp.exe(其存在的目的就是专为完成此事)īeyond Compare can be configured as the external difference utility in many popular VCS applications. But it is worrying to see it more complicated to newbies of all sorts.Using Beyond Compare with Version Control Systems It is good to see Moodle more scalable and structuring. The Moodle main strength was in shallow learning curve, easy to install and use, easy to mod or write plugin. That means less teachers-more programmers in Moodle development, and while it has obvious benefits the fate of SAKAI, created by professional developers on structured principles should teach us something. You, of course, could use git steeper learning curve to "weed out" contributors like Joseph (some even well know that I'm not the one to like his form of contribution at all - but they still attract quite a number of users) - the question is did you really want it. Git may have some more complex internal features (used only rarely and with greatest care), but Mercurial is well known for good UI (stable and good TortoiseHg and - as far as I read - great Eclipse plugin too).Īlso, while I don't have a command-line phobia, I find GUI quite useful when looking on colored diff's or cherry-picking changes by mouse etc. Using git or Mercurial will weed out the really clueless people who want to contribute )Ĭoncerns like Joseph's one is the things why I started this thread. (In the short term, it will be a useful filter. So, I would not worry about the learning curve. More and more projects are moving to git (or Mercurial) so it will become one of those things you just have to know if you want to join the open source world, like SVN and CVS are now. gitorius is better from an open-source purist's point of view. However, that infrastructure is not open source, which sucks. I particularly like the ability to comment on patches. Github is a very nice web interface and workflow. (I have no idea if these things work as well in Mercurial, but I assume it is not far off.) Things I rate highly are: speed, its facility merging and re-basing, the open-source workflows it enables. I have only used git, and it is fantastic. Compared to that difference, the differences between Mercurial and git are marginal. Well, any distributed VCS is almost infinitely better than any non-distributed VCS. I'll also add that, when I switched from SVN to git about six months ago, I found that I could scrape out a bare bones basic workflow with "cheat sheets" and some instruction from my co-workers, but I had no idea what the commands were really doing until I spent several hours reading the O'Reilly git book. It was actually a pretty similar experience to when I first started using git at the command-line, just figuring out the different workflow that comes from the basic conceptual differences between the systems. Having used CVS and SVN extensively in Eclipse in the past, I found that it was a little tricky adjusting to git in Eclipse. NetBeans is fine with this I just have to remind it to refresh its git status occasionally. For all the other operations (merging, branching, history, remote repositories), I switch over to the command line. I've got the NetBeans git plugin (nbgit) installed, but I only use it to do the equivalent of "git status" and "git diff". I've been using NetBeans lately but I was checking out egit last week, and at first glance it seemed a lot nicer and more mature than the NetBeans git plugin. The big Eclipse git plugin is egit, which is now an official Eclipse subproject. ![]() I totally agree that any conscious choice will be better than CVS! I hope they will be switched off on Moodle server. ![]() I also don't like much some things git allows you to do on repository, mercurial 'history is sacred' approach may be better. (Was contrib developers at least notified that they should be ready to switch VCS in two months or they just will know that as the fact once it done?) ![]() Is there extensive docs for them in place? Or contrib will remain in CVS? Or it's considered their problem and they just should adopt as best as they could? I don't tell it's should necessary affect VCS choice but than it should affect migration process. Are any thought given about them concerning this migration? I personally can handle any version control system (I hope), but I know well that not all contrib developers are professional programmers and they may have problems with unknown software, while git are not particulary good for newbies, especial without unix/programming experience. There is one more group of people: contrib developers with write access to the CVS. "it's also important to note that the shift really only concerns those with WRITE access to Moodle core code - those with read-only access will still be able to use a CVS mirror" ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |