-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John Nagle <nagle@animats.com> writes:
Actually, I was a bit incorrect here. The problem does seem
to go away if the sandbox is replaced.
But the problem is induced by an incorrect timestamp on
a commit from one client, and affects other clients via the
server. It's apparently possible to check in with a timestamp
in the future from the server's perspective, which causes
problems. A clock inconsistency check on commit would prevent
this problem.
The timestamp should be the time on the server if you are using :ext: or
:pserver:, I would expect only :local: over NFS or SAMBA to pay
attention to the client's time unless something like the '-d' switch is
used on a cvs import.
If you have a consistent method to reproduce the problem, please give a
step-by-step set of commands to do it.
If you have a patch for your problem, feel free to submit it.
Thanks,
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQE/2sS53x41pRYZE/gRArE2AKCXSRPpfkJ8IngHGKOd85lyqxGXeQCgwOhz
/sYB0wOFaEudHIpJEQSfbP0=
=Z4Iv
-----END PGP SIGNATURE-----