On 11/20/10 13:19, Joost 't Hart wrote: Hi!
[...] > The concept suggests more than plain CVS can do for you, and using my > (cervisia) CVS client I cannot find any trace of these patches. Each > file has its own private history, which is nice and necessary, but imho > clearly not sufficient. I don't want to break off a war here what is the correct versioning system. IMHO the important point is that there is any. > This is also the reason why I always vote for using SVN (subversion), > which works in terms of tree revisions. SVN has also some drawbacks. The main advantage of cvs is that it is pretty slick and doesn't dump down megabytes of metadata every time you uptdate your tree and is available everywhere easily, most likely already installed. It's so to speak the smallest common system. Back then when we decided on cvs instead of svn one major point was that it is small. I used a gsm-line back then and used that connection to the net for more than 2 years. I still use it now from time to time if I check into the repository while traveling. > Underneath there is - of course > - file version management, but that is only to save disk space, so to > speak. Within SVN patches can really be associated to any number of > files that were updated as a single impartible (sort of, and if the > developer behaves well...) action. In cvs you'd have to use releases for this. > Now the question: Is this patch list a bit of a brag, or is there > something that sourceforge adds to plain-CVS that we somehow did not > enable? @sf it is listed as cvs but as far as I got it they use another version system inside. I can switch on various featrues in the project admin, also other version control systems (git, mercurial, bzr, svn). I do not know if there is a seemless conversion however, that is if it is enough to just switch on git and be done. Sounds like that, but I admit that I do not really like to play with our software repository at the moment. It simply works. And I also admit that I'm no guru in version control systems. I use cvs for years now and I'm comfortable with it. > Note that the patches in the list all link to the root of the > repository tree display. They do not carry even the commit text > description. They tell us "something" has changed "then" by "him/her"; > but not what or why. cvs lists this information at the end of the day. > Or does the patch list simply assume that a projects uses SVN > (sourceforge supports it, of course), in which case the concept of a > patch could really be meaningful... AFAIK(!) it is generated while converting the cvs input to sf's internal version system. I think while ago this was svn I'm not sure they use svn today. I think they'd most likely use git. They offer cvs and svn to the users of course. cu Alexander ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
