Avoiding excessive compiling after a rebase

[Idan Kamara]

On Fri, Jun 17, 2011 at 1:21 PM, John Jefferies
<john.jefferies at globalgraphics.com> wrote:
> Thankyou Andrei, this looks like it will do exactly what I want (and I don't
> know how I missed it).
>
> Unfortunately, when I try "hg qtimes -s" I get an exception. I presume
> there's something I'm missing and I hope the info in the exception makes it
> obvious to you or someone. FTR. I have 7 patches applied, with 19 changed
> files.
>
> Thankyou
>
> John
>
> -----------------------------
> ** unknown exception encountered, please report by visiting
> **  http://mercurial.selenic.com/wiki/BugTracker
> ** Python 2.6.6 (r266:84297, Aug 24 2010, 18:13:38) [MSC v.1500 64 bit
> (AMD64)]
> ** Mercurial Distributed SCM (version 1.8.2)
> ** Extensions loaded: fixfrozenexts, onsub, relink, graphlog, rebase, mq,
> color,
>  transplant, extdiff, purge, qtimes
> Traceback (most recent call last):
>   File "hg", line 36, in <module>
>   File "mercurial\dispatch.pyo", line 16, in run
>   File "mercurial\dispatch.pyo", line 36, in dispatch
>   File "mercurial\dispatch.pyo", line 58, in _runcatch
>   File "mercurial\dispatch.pyo", line 601, in _dispatch
>   File "mercurial\dispatch.pyo", line 406, in runcommand
>   File "mercurial\extensions.pyo", line 178, in wrap
>   File "hgext\color.pyo", line 223, in colorcmd
>   File "mercurial\dispatch.pyo", line 655, in _runcommand
>   File "mercurial\dispatch.pyo", line 609, in checkargs
>   File "mercurial\dispatch.pyo", line 598, in <lambda>
>   File "mercurial\util.pyo", line 433, in check
>   File "mercurial\extensions.pyo", line 133, in wrap
>   File "mercurial\util.pyo", line 433, in check
>   File "hgext\mq.pyo", line 3049, in mqcommand
>   File "mercurial\util.pyo", line 433, in check
>   File "F:\Zip-files\Mercurial\qtimes\qtimes.py", line 24, in times
>     files, matchfn, anypats = cmdutil.matchpats(repo, pats, opts)
> AttributeError: 'module' object has no attribute 'matchpats'

Looks like that extension wasn't updated since early 2008.
Fixing it seems trivial though: see http://selenic.com/repo/hg/rev/5acbdd3941c4