23:07 <twb> You know, what I really want is a way to visualise, like a venn diagram, which patches are in each of my branches
23:07 <kowey> darcs pull --dry-run
23:07 <twb> kowey: I have 15 branches
23:07 [Heffalump would like that too]
23:07 <kowey> :-)
23:07 <twb> kowey: where am I pulling from?
23:08 <twb> It doesn't even have to list the individual patches
23:08 <kowey> just how the branches relate to each other?
23:08 <twb> Right
23:08 <twb> So I can look and immediately see that darcs-unstable+make/ is the union of darcs-make and darcs-unstable plus a small amount that's not in either
23:09 <twb> (that small amount being the conflict resolving patch)
23:09 <kowey> it's a cool idea
23:09 <twb> It means that I can see immediately that it's not safe to delete darcs-unstable+make because I'd lose a patch
23:09 <twb> I'm going to dump it on the BTS so it doesn't get lost

Just draw empty circles for each patch that, when clicked on, will
show the output of "darcs pull --dry-run --all x y" or something.

This sounds really cool, but I think this is strictly speaking not our bug.
It'd make a good use case for the darcs library though.  Perhaps it'd be a good
idea to create a wiki page listing the cool things we could do if we had a darcs
library.

On Tue, Aug 18, 2009 at 09:00:18PM +0000, Eric Kow wrote:
> Perhaps it'd be a good idea to create a wiki page listing the cool
> things we could do if we had a darcs library.

+1 for moving this wishlist bug into a "cool uses for libHSDarcs"
article on the wiki.

On Wed, Aug 19, 2009 at 02:03:26 +0000, Trent W. Buck wrote:
> +1 for moving this wishlist bug into a "cool uses for libHSDarcs"
> article on the wiki.

I've thrown together a quick
  http://wiki.darcs.net/Library