Fine, but myself and the couple of other people who want to work on this don't have commit access to a branch on svn, so one of the many features of Git is it allows us to easily setup a repository, and branches, while tracking the Wicket repo, allowing us to collaborate much more effectively than exchanging patch files.
Having a branch what we could commit to on the apache wicket svn would alleviate a lot of those issues, but that's probably not going to happen. I'm not going to hi-jack this thread, but there are multitudes of reasons why Git > SVN. I'm kind of surprised by your comments Jonathan as the person who started Wicket after all :) 2008/10/10 James Carman <[EMAIL PROTECTED]> > On Fri, Oct 10, 2008 at 11:35 AM, Jonathan Locke > <[EMAIL PROTECTED]> wrote: > > -1 > > > > i'm sick of new version control systems. i want simple eclipse > integration > > and since SVN finally works for me i wish people would stick with it. > > Agreed! The git vs. svn discussion had been done before in different > ASF forums and the bottom line is that the ASF uses SVN (currently) > for its version control. Also, since source work is not supposed to > be done "behind closed doors" (ASF is all about community) it's best > if the work is done using the SVN repository. > -- ___________________________ http://stubbisms.wordpress.com/
