Running "darcs changes --context" seems to ignore --human-readable and
--xml-output, perhaps as it should, but then the documentation is wrong.  I'm 
not sure which way this goes.

Quoth the source (Darcs/Command/Changes.lhs):

190 changelog opts patchset (pis, fs, errstring)
191     | Count `elem` opts = -- ...
192     | MachineReadable `elem` opts =
...
196     | XMLOutput `elem` opts =
...
263 changes_context repository opts = do
...
267     putDocLnWith simplePrinters $ changelog opts' NilRL ...
...
270     where opts' = MachineReadable : opts

And the dox:

255 ... Note that
256 while the \verb!--context! flag may be used in conjunction with
257 \verb!--xml-output! or \verb!--human-readable!, in neither case will darcs
258 get be able to read the output.  On the other hand, sufficient information
259 \emph{will} be output for a knowledgeable human to recreate the current
260 state of the repository.

The point is that because opts' includes MachineReadable, changelog will
match that guard before any other (except --count, which is forbidden with
--context earlier).  Thus --xml-output and --human-readable are effectively
ignored.

--nwf;

It's a bug in the documentation.

David, you said it is a bug in the documentation. But applied my patch which
fixes the problem.

I suppose either the patch should be reverted (and documentation fixed) or
documentation is correct (at least now).

Another question, should I feel free to close bugs that are (supposed to be)
fixed by my patches?

> Another question, should I feel free to close bugs that are (supposed to be)
> fixed by my patches?

Not only should you feel free to do this, you should also consider
starting the relevant patch names with 'Resolve issueNNNN', so that it
gets automatically picked up by the roundup-darcs integration that
Mark implemented.

(It also makes things easier in the future when we are trying to
figure out what happened in darcs's own history)

The following patch updated the status of issue995 to be resolved:

* Resolve issue995: changes --context : {--human-readable,--xml-output} have no effect.

I said it was a bug in the docs, but your change was pretty enough that I
decided to just apply it.  And yes, you can resolve any bugs you think are
fixed.  If you aren't certain, just add a note to the bug saying that you think
it should be closed, but aren't certain.  Plus what Eric said.  :)

David