I can't find the link now, but the apache git workflow is basically: 1) Clone your own 'master' branch from git.apache.org
2) Clone your 'master' and work off a local copy 3) Push to your master, and then dcommit using git-svn to push changes to svn. So basically, you still commit to svn, so the svn is always in sync. There's a whole page describing this somewhere on the apache docs I'm certain (I was reading it on friday) but I can't for the life of me find it now. ~ Doug. On Sat, Oct 15, 2011 at 5:19 AM, Nelson Silva <[email protected]>wrote: > Michael suggested git.apache.org as a mirror of the svn repo, which i > think > is great and they even get pushed to github https://github.com/apache > > But they say these are read only mirrors... how would the changesets be > commited in the svn repo? Patches? > > Personnaly i feel that github provides a friendly environment for newcomers > and might provide a much needed boost to Apache Wave. > On a side note i'd like to understand how much people are commited to the > project and where it's going... things have been really quiet in terms of > discussions and code commits... > No dia 14 de Out de 2011 20:36, "Michael MacFadden" < > [email protected]> escreveu: >
