darcs changes somefile --last 10 shows the subset of the last 10 patches that
affect somefile. It should show the last 10 patches that touched somefile,
because this is more intuitive to users and more often what you want.

Ack, I run into this every so often. I'll look into fixing this: however, if
anyone feels like fixing, go ahead, I am ever so short on time, so don't expect
quick turnaround. Sorry... (Feel free to reassign to yourself in that case.)

There's now changes --max-count that implements the behaviour you are looking
for. You may want to make a case for replacing the --last behaviour with --max-
since the max-count implementation should be fairly efficient, I don't think
that speed would be an argument in favour of keeping the --last as it is, only
possible UI confusion ... Eric, what do you think?)

I think there is a use for --last, which is to limit the search within the last
N patches.

This is probably a question for darcs-users.

For the moment, I'm happy to just leave it resolved.

There is a current proposal to

* remove the current --last matcher

* rename --max-count to the newly vacant --last

* suggest users who want the current --last to use --index=1-N instead; 
note that making this choice means that we'd be stuck with --number that 
counts backwards, cf. issue1484.  Alternatively, we could just do 
without.

The patch is further.  I suggest we discuss this further on darcs-users 
and/or a Darcs Hacking Sprint to make progress

Background: http://irclog.perlgeek.de/darcs/2010-08-18#i_2718230 (stop 
at 12:50)

BTS training: this ticket is marked need-action, which means we have a 
concrete action in mind.  In this case, the action is "hold a discussion 
on the proposed change".  After the dust has settled, you can flip the 
bug to "need-implementation".  Not all UI changes need discussion.  
Sometimes at your discretion you can decide that it's more expedient to 
have the implementation first and the discussion after that.