cvsps: better use of commitids - and a wrinkle in testing

[Bryan O'Sullivan]

On Wed, Jan 16, 2013 at 1:28 AM, Frank A. Kingswood
<frank at kingswood-consulting.co.uk> wrote:
> I think the commitid is likely to include the date in the hash, so I fear
> that the output of this test may not be stable between runs. If this is
> true, how could we cope with two valid outputs of the glog test?

I'm definitely seeing that test-convert-cvs-synthetic.t is not stable.
It doesn't seem to be possible to synthesize dates with "cvs commit",
so I'm not sure what to do about this. Maybe just not run "hg glog"?