[ANNOUNCE] bzr-gardener: A new way to manage lots of branches and working trees

[Russ Brown]

On Fri, Sep 17, 2010 at 4:43 PM, Vincent Ladeuil <v.ladeuil+lp at free.fr> wrote:
>>>>>> Russ Brown <pickscrape at gmail.com> writes:
>
> <snip/>
>
>    >> Can you post the output of 'bzr info -v' for such a branch ? Does it
>    >> mention either a submit branch or a parent branch ?
>    >>
>
>    > I think in my case it is probably a case of it choosing the "wrong"
>    > option out of the submit and parent branch.
>
> Really ? What workflow are you using to end up with a submit_branch
> which it no the target of the merge for your branch ?
>
> Did your submit branch got set up "wrongly" by doing an "unrelated"
> merge ?
>
>    > In my case it was checking against "submit", when "parent" would
>    > have been more sensible. I'll see what falls out of bug 641043
>    > before filing anything about it though.
>
> Please comment on it explaining your setup, it's the best place to
> collect all the various use cases.
>

Actually, the one I looked at may not have been the best example (a
branch of a branch). I have a *lot* of branches in this directory that
need cleaning up: I think I'll do that and then run gardener on what's
left and see if I can find any artifacts. :)

-- 

Russ