On Tue, Nov 3, 2009 at 03:26, Carlo Marcelo Arenas Belon <care...@sajinet.com.pe> wrote: >> I notice it can do some handy tricks, like generating version numbers that >> reflect the tag you are building in > > it can also do some more interesting tricks, like pushing/pulling from a > subversion server and so there is really no need to force anyone to migrate > either.
So basically, if you (plural) want to use git, go right ahead. As a project, it may need a bit more discussion, and at least some setup work. I would suggest having both systems run in parallel for a short while before cutting over. Pick a revision in the SVN tree as a base for the import/export to git, and make sure that all of the history, tagging, branching, etc is preserved. Then for a short while (few weeks? a month?) run both systems in parallel, and make sure the developers make *TWO* checkins. One for SVN, one for git. Yes, it's a hassle--that's why the transition time is short. :) -- Jesse Becker ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
