I don't think I voiced an opinion in that message. :) For Apache Wicket, using git as the main repository is not yet acceptable. I don't know about tool support for Eclipse and windows, I don't use windows, and commandline scm is something I really don't mind. I don't miss having to install a plugin for scm support.
I don't want to exclude a (large) part of our community and committers by switching to git. Martijn On Sun, Mar 1, 2009 at 11:20 PM, Jeremy Thomerson <[email protected]> wrote: > So, you have reversed your opinion of git? [1] > > Should a vote be done first? Seemed like several (including yourself) > didn't like the idea of switching to git at that time. > > [1] - > http://www.nabble.com/Finishing-Portal-2.0-development-tt19909563.html#a19921559 > > -- > Jeremy Thomerson > http://www.wickettraining.com > > On Sun, Mar 1, 2009 at 4:12 PM, Martijn Dashorst <[email protected] >> wrote: > >> All, >> >> sf.net supports git as a SCM. I've used git on some small projects >> locally, and I like it: local commits are really nice, (proper) merge >> tracking shortens branch management, it is really fast and finally >> committing small parts from your local copy is much simpler than with >> svn (cherry pick the files to be added). >> >> Though svn was a great improvement over cvs, I think git is a boon to work >> with. >> >> Anyone up for migrating the wicketstuff svn repository over to git? >> >> Martijn >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.5 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.5 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
