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:
Hi! On 07/10/2008 01:35 PM, Jasper Groenewegen wrote:In that case I apologise for the inconvenience I've caused. And Aaron, thanks for BB, I find it a very useful tool. (Not that I have experience with contributing to other projects, but still. :) ) So my workflow would now be bzr-gtk/trunk$ bzr update bzr-gtk$ bzr branch trunk feature bzr-gtk/feature$ <hack hack hack> bzr-gtk/feature$ bzr commit -m "Fix feature"But which of the following options work: bzr-gtk/feature$ bzr send -o ../feature.patch lp:bzr-gtk bzr-gtk/feature$ bzr send -o ../feature.patch lp:bzr-gtk/trunk bzr-gtk/feature$ bzr send -o ../feature.patch https://code.launchpad.net/~bzr-gtk/bzr-gtk/trunk ? Please say option 1 :D Oh, and if there are other things I could do better.. let me know!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
