Hi, In this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257706 Denis (Eclipse webmaster extraordinaire) asks if any projects would like to beta test a move to git. Here are my reasons _for_ participating: - many FOSS projects are already using git and thus people are familiar with it and thus will hopefully be more likely to contribute to our project if they know how to use/contribute with git - it makes it easier for some distributions to track eclipse-build (Debian is already doing this) - we can maybe get hooked up with Gerrit a la http://egit.eclipse.org/r - we can help dogfood EGit which is very important to increasing the contributor base with existing FOSS hackers - if we mess up, we still have our SVN repo And why I'm against it: - EGit isn't yet as ready for prime time as Subclipse is - I'll have to re-do some of the configuration of our Hudson-based builds - it may require use of command line git - there will be a learning curve - I'm not entirely sure we'll get to keep all of our SVN history (which admittedly isn't complete as many projects came from elsewhere and we lost _that_ history on import) - some committers using SVN, some using git (not sure if this is a real problem or not) What are your thoughts? Will it be easier/harder for you to contribute if we move to EGit? If you have to drop to the command line to do things, will that deter you from contributing/committing? Should we move/not move? Andrew _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
