Let me point out another nice feature of git: git provides server-support to behave to clients like a cvs and/or svn server. This means, one can access the git repository from cvs or svn (or git) clients. Not sure if this is an issue, but a user who does not want to learn new commands can contiune to use the CVS interface.
I personally like git for its speed and simplicity to setup and usage. Git has certain ideosyncharies (e.g. does not like empty directories), and the downside is that if the full feature set of a more distributed scm is used, things become quite complex, at least for a casual user. just my 2cent -gustaf Ibrahim Tannir schrieb: > FWIW, to let my paranoia out: > > I don't like SVN because it obscures and packs the whole > repository into one big file, which IMHO overshadows all its > benifits. > > I've been able in tha past to resolve the consequences of quite a > few CVS bugs, due to the open structure of its repository. > > OTOH, if we're to continue using the services of SourceForge for > the Naviserver project and Vlad, Stephen and Zoran who do most of > the work are dissatisfied with CVS... > > I think at some point, there were contemplations to move the > project to some local machines. Vlad was offering to host it, > wasn't he? We (Zoran and I) at ARCHIWARE could offer a mirror > too. In that case, we can consider going for other source control > systems (GIT?) etc. and away from both CVS and SVN. > > Ibrahim > ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
