When interactively browsing patches during ask-for-deps, it should exclude
patches which I already depend on because they are depended on by patches that
I've already selected.  Also, of course, it should exclude patches that it
already depends on because they are syntactically required.

For some reason ask-for-deps is extremely slow (http://bugs.darcs.net/issue89)
even though it doesn't do these things for me.  Actually, maybe there is
another bug here: it says it is going to ask me for deps on 779 patches, when
there are actually 1375 in the repo.  Has it already calculated the maximum
number which I could possibly choose to depend on or something?

Regards,

Zooko

This sounds like a regression bug.  --ask-deps was broken in
some very old version of darcs but got fixed and then worked as
it should (not asking about explicit or forced dependencies).
It however always has been slow with many/complicated
dependencies.

I did some simple testing with both stable and unstable,
but couldn't see any faulty behavior.  Can you produce a test
case or supply the repo?

My apologies -- I must have misunderstood something last night.  In the morning
light, --ask-deps does indeed excluded already-depended-on.

Also this explains why it is so darn slow.

resolved.  bug reporter mistake.

Oh, I see at least partially why I was confused last night -- it doesn't update
the count of patches remaining as I add deps.

resolved