Please review the following regarding Apache SVN Git Mirrors: http://www.apache.org/dev/git.html
I think this should ease the transition to SVN. I believe according to the Apache process we really do need to move in to SVN for the time being. The question is when and how are we going to do that. On May 25, 2011, at 2:47 AM, Thomas Broyer wrote: > 2011/5/24 Paul Lindner <[email protected]>: >> You can clone the apache git mirror and send pull requests that way. It's a >> little more work for the committer but it is doable. > > Just stumbled on this wiki page (while looking for something totally > unrelated): > https://cwiki.apache.org/MAVEN/example-git-svn-workflow-for-maven.html > (the "maven" here is about the Apache Maven project itself, not about > projects using Maven as the build system) > > That being said, I'm very happy with git-svn and git-cl when working > on GWT's code base (no committer rights; the GWT team uses git-p4 and > they have a job that replicates internal perforce commits to the > public svn repo), so that's probably what I'd use when the code is > moved over to SVN (I'm not used to DVCS, and I might very well be > missing something from not using github more, I'll give it a try if > it's an option for Wave) > > -- > Thomas Broyer > /tɔ.ma.bʁwa.je/
