Some of our projects check out dozens of top-level CVS modules. So our console
output often has such meaningful entries as

$ cvs -q -z9 update -PdC
$ cvs -q -z9 update -PdC
P build.xml
$ cvs -q -z9 update -PdC
$ cvs -q -z9 update -PdC
$ cvs -q -z9 update -PdC
$ cvs -q -z9 update -PdC
$ cvs -q -z9 update -PdC
P build.xml
$ cvs -q -z9 update -PdC

Hmm, what was it updating now?

It would be preferable to run CVS update just once, at the top level, which
would probably be faster and also print more informative paths. But in any case
it would also be helpful to see what dir a command is being run in. Attaching
(as yet untested) patch which should give that information succinctly and be
useful in our case at least.