>>>>> "Jasper" == Jasper Groenewegen <[EMAIL PROTECTED]> writes:
Jasper> Elliot's solution was correct except for the third line which
Jasper> should be excluded.
Jasper> To conclude this issue in a referable way:
Jasper> When you want to help fix bzr-gtk multiple times and use a bzr
Jasper> repository so all the revisions are stored together:
Jasper> $ bzr init-repo bzr-gtk
Jasper> bzr-gtk$ bzr checkout lp:bzr-gtk trunk
Jasper> create ~/.bazaar/locations.conf and put inside:
Jasper> [/path/to/bzr-gtk]
Jasper> public_branch = https://code.launchpad.net/~bzr-gtk/bzr-gtk/trunk
Jasper> Now for each new feature:
Jasper> bzr-gtk$ bzr branch trunk feature
Jasper> bzr-gtk/feature$ <hack hack hack>
Jasper> bzr-gtk/feature$ bzr commit -m "Created/fixed feature"
Jasper> bzr-gtk/feature$ bzr send -o ../feature.patch
Jasper> and send the created feature.patch to
Jasper> [EMAIL PROTECTED], starting the subject with [MERGE].
Jasper> Hopefully no comments on this one anymore :)
One more :-)
Since you use thunderbird, your last step could be further
simplified and become:
bzr send
Which will open a new mail containing a subject with the first
line of your last commit message and the patch as an attachment.
All you need to do is configure the mail_client variable in
bazaar.conf:
bazaar.conf:
------------
[DEFAULT]
mail_client = thunderbird
You can also do:
bzr send --mail-to [EMAIL PROTECTED]
Here again, that email address can be configured in various ways
(which I don't remember right now :-) in either locations.conf or
branch.conf.
Vincent
--
bzr-gtk mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.canonical.com/mailman/listinfo/bzr-gtk