1. Summarise the issue (what were doing, what went wrong?)
 Annotate on directories prints unknown as the corresponding patch of a
file, in certain cases. 
2. What behaviour were you expecting instead?
 Annotate is to give the last patch that modified the file in the directory.
3. What darcs version are you using? (Try: darcs --exact-version)
 darcs 2.8.0
4. What operating system are you running?
  ubuntu 12.04

Sample test case added.

Attachments

• add-test-for-issue2207.dpatch

Bug fix.

Attachments

• resolve.dpatch

bsrkaditya, if you `darcs send` the patches (with a patchname "resolve
issue2207") the tracker will pick them up, and assign them to the relevant
issues.

> [Fix issue2207: Annotate on directories
> ...
> -       else return $ (seal $ newset2RL r, recorded, toFilePath origpath)
> +       else return $ (seal $ newset2RL r, recorded, "./" ++
toFilePath origpath)
> ...
> -        A.annotateDirectory (invertRL patches) (fp2fn $ "./" ++ path)
subs
> +        A.annotateDirectory (invertRL patches) (fp2fn path) subs
> ...
> -                        putStrLn $ fmt con $ A.annotate (invertRL
patches) (fp2fn $ "./" ++ path) con
> +                        putStrLn $ fmt con $ A.annotate (invertRL
patches) (fp2fn path) con

I feel dubious about these ("./" ++) applications; is this sort of thing not
centralised in some path-sanitising code? If not, perhaps it should be...