2009/2/27 Russel Winder <[email protected]> > Tom, > > On Fri, 2009-02-27 at 13:49 +0100, Tom Eyckmans wrote: > > > > > > 2009/2/26 Adam Murdoch <[email protected]> > > > > > > Tom Eyckmans wrote: > > > I've updated the http://docs.codehaus.org/display/GRADLE/How > > > +to+contribute+a+patch+to+Gradle page on our Wiki. > > > > > > Feedback is more than welcome. > > > > > Thanks for doing this. > > > > I think it's a little odd that I have to use a particular > > developer's repository, which may or may not be up to date, > > and may or may not have other changes in it. > > > > > > Personally I reserve the master branch for tracking SVN trunk and only > > merge feature branches with it when I am ready to commit to SVN. > > I too follow this protocol. > > I also try to do it with maintenance branches but to avoid the plethora > of branches sometimes don't for them.
That is understandable. > > > > Is it possible to set up a repository on github which is > > automatically synchronised with svn? > > > > > > I don't think so, I haven't seen any Git hosting that provides this > > anybody know of a hosting service with this feature? If needed I could > > setup a cron job to sync stuff. > > I had thought that Kevin O'Neill had set up a Groovy mirror repository > that does auto update on GitHub. Perhaps he does it with an external > cron job? Perhaps it would be better to plugin some logic into the svn commit hook so to remove the need for polling? Is this possible at codehaus? > > > > Or is it easy for someone to create an empty repository and > > sync it with svn manually? > > > > > > I have to do some testing with this. I already tried to clone my repo > > on GitHub and on the new clone the information about SVN is not > > available, so I had to configure the SVN sync again, I do have look > > into this some more because I don't know how this new repo will relate > > with the original repo and if work is easily shared. I also have to > > test this with a forked repo via GitHub. > > I think Git, Bazaar and indeed Mercurial behave the same, a clone is > always a clone of the parent you cloned from and all information about > the parents parents get lost. > > I have to admit to having always done a Bazaar branch or a Git clone > from the original Subversion repository. I suspect that Gradle, Gant, > indeed Groovy are still sufficiently small that doing an original is > faster than sorting out a re-parenting. > > I find working with individual branches on Launchpad for exchanging > changesets between development branches straightforward to understand. I'm not sure on how the changes on the dev branches get committed to svn could you explain how this works because I don't have experience with Bazaar on this point. > > Is there an easy explanation of how to do the same with Git? > I think if we could get a dedicated repo up on GitHub for the svn sync it would work in the same way. But still don't know how the parenting issue is solved with Git, perhaps that falls into place when I understand the Bazaar way of working. > I must > admit to only having used Bazaar as a DVCS, my use of Git has always > been as a direct Subversion client or simply to to a read only mirror of > someone else's repository. > > Thanks. > > -- > Russel. > ==================================================== > Dr Russel Winder Partner > > Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203 > 41 Buckmaster Road, f: +44 8700 516 084 > London SW11 1EN, UK. m: +44 7770 465 077 >
