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

[Russ Brown]

This looks really useful! I have a couple of questions though.

How does it determine "merged"? For me, "merged" would mean the branch
has been merged to a specific other branch (i.e. trunk, or similarly
purposed). It doesn't seem to be doing that though: it's marking
plenty of branches as "merged" that I don't consider to be merged at
all.

Also, for checkouts where the branch it is bound to has disappeared,
it is erroring (exception: Not a branch). Maybe it would be cleaner to
mark these as something like "orphaned"?

On Wed, Sep 15, 2010 at 7:43 PM, Martin Pool <mbp at canonical.com> wrote:
> That sounds nice.  One thing I'd really like in it is to match my
> branches against bugs and infer things from that: if the bugfix branch
> is now merged in to the trunk or series branch, perhaps the bug should
> be closed.  (But not necessarily, because I might not really have
> fixed it.)  If I have a branch for a confirmed bug with some changes,
> perhaps the bug should be assigned to me and inprogress?  etc.
>
> I'll try it out...
>
> --
> Martin
>
>



-- 

Russ