one byte change to file not detected ?

[Ken Blake]

If you set the date of the file to to time when it was checked in, then
won't your problem go away?

I'm also wondering if you are doing all the revisions of file A, followed by
all the revisions of file B, etc.  This will end up with a very strange
looking revision history for the mercurial repo.  It would be better to
first compile a list of all files, their revision number, and check in
date.  Then sort this list by the date.  Now commit each change in the order
it was originally done.  For extra credit, group the files with close
checkin dates, same author, and same check in comment, as a change set and
commit together.

Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080220/180c2ab2/attachment.htm