Timestamp fuzz on CVS commits?

I've been trying to figure out if and where cvs2svn applies a little
fuzz on CVS revision timestamps to merge chronologically adjacent file
revisions into changesets.  That is, if

  cvs commit file1 file2 ... fileN

takes 3 seconds to run, the resulting file revisions will span 3 sec,
but really should become 1 changeset.

I couldn't figure it out from the code... so 1) is a little fuzz
applied to the timestamps, and 2) if so, where?

(Asking because I would like to increase the fuzz boundary a bit.  I'm
seeing changesets in my output Mercurial repository with the same user
and commit message, but different files and different timestamps.)

Thanks --

Greg

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2409015

To unsubscribe from this discussion, e-mail: [[email protected]].