On Mon, 2009-07-13 at 09:28 +1000, Adam Murdoch wrote: > > Jason Porter wrote: > > I noticed a little bit ago Gradle is trying to make Git it's official > > repo, maybe that's complete now, not sure. I'm wondering how best to > > go about contributing. I spent a few hours last night trying to > > understand how to create a plugin and a task for that notifier plugin > > I spoke about a few weeks back. Is the correct way now to ask for a > > clone or a fork of the git repo then merge back? Or should I still be > > working off of the svn repo and submit patches? I guess I should have > > read > > http://docs.codehaus.org/display/GRADLE/How+to+contribute+a+patch+to+Gradle > > first :) I'll follow the directions there. Though it may be good for > > the community to hear the "official" answer to this as the wiki > > details many ways of contributing. > > > > > > I don't have an 'official' answer. Personally, I prefer to review > changes using git, but svn is completely fine as well. It depends on the > size of the change - I think git is easier for everyone for large > changes (like a new plugin, for example).
I would:
g/git/s//Bazaar/
but only ed users will understand :-)
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
