Alex Schuilenburg <al...@ecoscentric.com> writes: > Øyvind Harboe wrote on 2009-09-17 11:52: >> Does anyone know a reason not to switch to git for eCosForge? >> >> My thinking is to use http://repo.or.cz/ to host projects. >> >> www.ecosforge.net uses a version of subversion that is getting >> a bit long in the tooth (1.4) and I'm just wondering if >> git isn't a better choice anyway.... >> >> The plan is to leave the current subversion repository as-is and >> let migration happen eventually, deleting old repositories(they >> are still there in the history) after migration to git. >> >> The idea is to have one git repository per eCos repository(or >> project if you will). >> >> The first project I would like to switch to git, is nios2ecos. > > Why git in particular?
Because it's simply the best? ;-) > We have started looking at switching to another RCS at eCosCentric as > well. In particular I looked at three distributed RCS solutions: git, > bazaar and mercurial. While there is no doubt that git is the most > powerful of the three solutions and also fastest on linux, it is also > the most complex of the three solutions with a very steep initial > learning curve, it's support for windows is lacking, and its > documentation is sparse and confusing. As a tool for experienced Linux > developers, sure, git is the best choice. But for the average eCos > developer, I am not convinced. Did you see this: <http://code.google.com/p/msysgit/> (I'm not Windows user, so didn't use it myself). BTW, git has gitcvsserver: <http://www.kernel.org/pub/software/scm/git/docs/git-cvsserver.html> so those who are used to CVS and don't wish to learn new tool can continue to use their favorite CVS clients. -- Sergei. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
