A user on IRC noted that he had problems with darcs get --to-match.  His log is
below:
I'm having a problem getting using --to-match and a specific date

transcript of shell activity follows
----------
[orig]$ pwd
darcs-test/orig
[orig]$ darcs changes
Sun Jun 18 14:14:03 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Changes 02

Sun Jun 18 14:12:32 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Changes 01

Sun Jun 18 14:11:43 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Initial revision.
[orig]$ cd ..
[darcs-test]$ darcs get --to-match 'date "Sun Jun 18 14:11:43 EDT 2006"' orig new
Copying patch 3 of 3... done!
Unapplying 0 patches.
Finished getting.
[darcs-test]$ cd new
[new]$ darcs changes
Sun Jun 18 14:14:03 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Changes 02

Sun Jun 18 14:12:32 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Changes 01

Sun Jun 18 14:11:43 EDT 2006  Fred Bloggs <fred@bloggs.invalid>
  * Initial revision.

Annotations for this paste:

Annotation number 1: 	get problem (more)
Pasted by: 	Dino_
	5 seconds ago
	Context in IRC logs
Paste contents: 	Raw Source
[new]$ darcs --exact-version
darcs compiled on Apr 15 2006, at 14:34:51
# configured Tue Feb 28 07:02:39 EST 2006
./configure --no-create --no-recursion

Context:

[TAG 1.0.6
Tommy Pettersson <ptp@lysator.liu.se>**20060228111841] 

----

Note that I can replicate the same behaviour with darcs 1.0.8.  Note also that
darcs works as expected when the dates are somewhat far apart, that is, not down
to the minute like this one.

This bug is superceded by issue31, which now reports basic brokenness for date
parsing with Darcs2.

Once that bug is fixed, we'll see if there is more to do here.

I bet the underlying causes of this are improved with the issue31 fixes, but
there are still a choice between two ways we can close this ticket:

(a) fix the documentation bug - the documentation does not make it sufficiently
clear that darcs only supports matching up to the same day

(b) implement a wishlist item - date matching should allow for finer granularity
matches.  We already have the code for partial dates, but it needs to be
extended for times as well as dates, and also for non ISO dates

I'm fine with the doc-bug resolution for now. We have enough other open issues
which can only be resolved with programming to worry about.

Doc note: the confusing bit here being that time-based matching works for
intervals, but not for simple date matches.

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

* Resolve issue187: Extend partial date matching to hours, minutes, secs.