Hi Spencer,
It should work very similar to the way things work on github. If you
have a launchpad account, you should be able to create your own branch from
the main one, and after you've committed your changes to it, you should be
able to propose a merge.
I'll put this on the wiki too as you suggested, but if you have a Launchpad
account you should be able to just do this:
[commands]
bzr branch lp:gradle-templates
cd gradle-templates
... fix my code ...
bzr ci -m "Fixing Eric's Code"
bzr push lp:~userid/gradle-templates/trunk
[/commands]
Just replace 'userid' with your Launchpad user id (eg. elberry). You can
also change 'trunk' to be anything.
Then visit your branch on launchpad, eg:
https://code.launchpad.net/~elberry/gradle-templates/test
You should see a link that says "Propose for merging". Click that and follow
the instructions there.
There's supposed to be a way for you to just email in merge requests, but I
haven't been able to get it to work for me yet.
https://help.launchpad.net/Code/Review#Email%20interface
You might have better luck though. From my understanding you would do this:
[commands]
bzr branch lp:gradle-templates
cd gradle-templates
... fix my code ...
bzr ci -m "Fixing Eric's Code"
bzr send lp:gradle-templates -o fix.merge
[/commands]
Then you would just email the fix.merge file to: [email protected] as
an attachment.
If you don't want to sign up at Launchpad, you can also send me the merge
directive directly.
Cheers, and thanks!
Eric
On Fri, Jun 3, 2011 at 6:12 AM, Spencer Allain <[email protected]>wrote:
> Good stuff. I've branched off your bazaar repo to grab and compile from
> source, which worked without any problems. I've noted a few things in the
> build, and would like to supply you with updates (but I'm both a bazaar
> novice and also do not have a current launchpad account).
>
> If I did sign up for a launchpad account, would I somehow post my own
> branch there in an area I'd create, or is there some way to write my forked
> branch to your current repository? Maybe you could add some steps to the
> wiki as to how you'd prefer collaboration be worked out for code
> changes/suggestions?
>
> I noticed that you have in the build.gradle a repository specified for
> mavenCentral(), but aside from the unused junit dependency, nothing else
> would ever have to reach out, and it compiles just fine by removing that
> resolver (and the junit dependency can also be removed unless you intend to
> use it later). There are some other things as well, when looking into the
> default templates, but it seems a much better idea for me to publish things
> as part of a branch, and let you decide which if any changes you'd like to
> keep.
>
> -Spencer
>
--
Learn from the past. Live in the present. Plan for the future.
Blog: http://eric-berry.blogspot.com
jEdit <http://www.jedit.org> - Programmer's Text Editor
Bazaar <http://bazaar.canonical.com> - Version Control for Humans
