The darcsver tool [1] generates a version number for your project  
based on the darcs history.  It looks for a darcs tag of the right  
format and if it finds it, it parses it to get the version number.   
Also, it counts how many patches there are in the repository to  
append "-r$NUMBER"  to the version (analogous to SVN's "revision  
numbers").

This latter feature is quite expensive -- every single time anyone  
builds or runs tests in the Tahoe project, the Tahoe build system  
invokes darcsver, which invokes "darcs changes --xml" and parses the  
output.  It takes seconds for "darcs changes --xml" to run, and this  
is the single largest delay in the process of running a quick test.

It would be great if there were a command like...

Uh, like "darcs query repo", which emits the count of patches in 0.05  
seconds.

Okay!  Thanks for using your time machine to fix this bug!

Regards,

Zooko

[1] http://pypi.python.org/pypi/darcsver

fixed by time machine

Does anyone know what was the earliest stable release of darcs that had "darcs 
query repo" which emitted 
"   Num Patches: 3601"
?

On Thu, Feb 12, 2009 at 21:55:54 -0000, Zooko wrote:
> Does anyone know what was the earliest stable release of darcs that had "darcs 
> query repo" which emitted 
> "   Num Patches: 3601"

Note also darcs changes --count

$ darcs changes -p '--count'

Mon Apr  7 16:18:25 BST 2008  David Roundy <droundy@darcs.net>
  * add --count output option to changes.

$ darcs changes -p 'show repo'

Fri Nov 16 06:24:53 GMT 2007  Kevin Quick <quick@sparq.org>
  * Added "darcs show repo" command to display repository information