On Fri, 2009-02-27 at 08:53 +1100, Adam Murdoch wrote: > > > 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. Is it possible to set up a repository on > github which is automatically synchronised with svn? Or is it easy for > someone to create an empty repository and sync it with svn manually?
Do remember though that in a sense it doesn't matter. Taking a clone of a Git repository or a branch of a Bazaar branch doesn't mean you can use a DVCS to develop for Gradle. Gradle's mainline is a Subversion trunk which means that Git and Bazaar can only be used as Subversion clients. This necessitates an immediate rebase of the Git clone or Bazaar branch against the Subversion repository and this more or less invalidates any normal approaches to using a DVCS. Currently the only way of using standard DVCS approaches where a Subversion repository is the master is to use Bazaar and store a Bazaar branch in the Subversion repository. Then the DVCS metadata gets stored. This cannot be done with Git. But Git is much faster at interacting with Subversion than Bazaar -- exactly because Bazaar can do so much more. All this is trade-offs. -- 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
signature.asc
Description: This is a digitally signed message part
