To conclude this issue in a referable way:
When you want to help fix bzr-gtk multiple times and use a bzr repository so all the revisions are stored together:
$ bzr init-repo bzr-gtk bzr-gtk$ bzr checkout lp:bzr-gtk trunk create ~/.bazaar/locations.conf and put inside: [/path/to/bzr-gtk] public_branch = https://code.launchpad.net/~bzr-gtk/bzr-gtk/trunk Now for each new feature: bzr-gtk$ bzr branch trunk feature bzr-gtk/feature$ <hack hack hack> bzr-gtk/feature$ bzr commit -m "Created/fixed feature" bzr-gtk/feature$ bzr send -o ../feature.patchand send the created feature.patch to [EMAIL PROTECTED], starting the subject with [MERGE].
Hopefully no comments on this one anymore :) Jasper Jasper Groenewegen wrote:
Hmm.. this seems to generate a # source_branch: https://code.launchpad.net/~bzr-gtk/bzr-gtk/testing line in the output file (from ~/bzr-gtk/testing)and using submit_branch instead of public_branch errors on bzr send because (...lp..)/bzr-gtk/trunk/testing is not a branch (duh)I try to find the right option in the user reference but I guess the way I branch and use send is not entirely the proper way :/Jasper Elliot Murphy wrote:
I think that you can set ~/.bazaar/locations.conf to have this entry: [/home/jasper/bzr-gtk] public_branch = https://code.launchpad.net/~bzr-gtk/bzr-gtk/ public_branch:policy = appendpath and that will make #1 work for you the desired way.
signature.asc
Description: OpenPGP digital signature
-- bzr-gtk mailing list [email protected] Modify settings or unsubscribe at: https://lists.canonical.com/mailman/listinfo/bzr-gtk
