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/trunkbzr-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! Jasper John Arbash Meinel wrote:
Vincent Ladeuil wrote: |>>>>> "Colbrac" == Colbrac <[EMAIL PROTECTED]> writes: | | Colbrac> The bzr-gtk/trunk folder is a checkout of the launchpad bzr-gtk/trunk | Colbrac> which I keep around as the basis for local branches in which I do | Colbrac> different additions to the code. | | Colbrac> As far as I can see bundle buggy | | We all love Bundle Buggy, to the point that some of us consider | it as kind of human not a mere bot. | | The truth is, it's really Aaron's puppet, so when Aaron talk | about BB behavior... well, consider that BB itself is not able to | find the right words and Aaron is just helping him/it. | | Vincent | The specific issue is that BB changed hosting to a shared location. There used to be 2 separate instances which meant that patches submitted could only be meant for a given project. Now that they are co-located, the only way to distinguish whether a patch is meant for 'bzr' or for 'bzr-gtk' is by its target branch. BB *does* pick up the patches, but I think the default rule is to consider them 'bzr' patches. Which means that we get the BB email on a different mailing list, and Aaron has to go in and manually change the target for the branch. So please, be kind to Aaron and set your public branch locations. John =:->
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
