* Mike Noyes <mhno...@frontier.com> schrieb: > Note: CVS doesn't scale well on the server side (per SF staff). > CVS can't do diffs of binary files.
CVS has lots of other (mostly fundamental architectural) drawbacks, eg.: * _only_ supports central-server workflows, no private repositories, so no downstream forks, requires server access for all operations (also applies to svn) * quite ugly branch concept, which makes it practically unusable (svn doesn't have real branches at all - it's just the client that uses subdirectories to minimic it somewhat) * lacks important operations like rebase, cherry-pick, etc (same for svn) * scales very bad on large repositories or long histories (svn isn't really much better) * no distributed workflows whatsoever (same for svn) * cannot interface with other VCS'es (same for svn) Git, on the other hand, supports all these things very well. So my vote is clearly for git. If some of you aren't yet used to it, just drop a note - I'll be happy to train you :) cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
