Hullo.

I would like dearly to have the ability to query darcs explicitly about the 
dependencies between patches.  Ideal queries that spring to mind would be
 * "for this unrecorded hunk, what will be its dependencies"
 * "for patch .... recorded locally, what are its dependencies"
 * "for patch .... recorded in remote, what are its local and remote 
dependencies" (i.e. "if I pulled this, what would come with it, why, and will 
there be conflicts")

It would also be fantastic if this command could produce human readable and dot 
input.

Thoughts are welcome; I'll look into adding this as time allows, but I wanted 
to ask others for input.

Sounds like a nice and doable idea.  

Promoting to feature, because I can imagine this making many people happy, with
little (?) implementation cost.  On the other hand, I am a bit worried about the
actual cost when this runs, but maybe this could just stop at the first tag or
something.

Bumping to 2.6.

I just ran into a need for this too: I want to unrecord a large (several 
megabytes) patch that imported some images, fonts etc, but I'd recorded 
several patches since. It turns out the original patch created a lot of 
the directory structure, which made it hard to figure out which subsequent 
patches depended on it. In the end I resorted to repeatedly running `darcs 
show files -p '...'` and manually inspecting the paths in each patch.