[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Commit inconsistency: Up-to-date check did not fail though it sho uld ha
From: |
Reinstein, Shlomo |
Subject: |
Commit inconsistency: Up-to-date check did not fail though it sho uld have ! |
Date: |
Tue, 18 Feb 2003 11:04:36 +0200 |
Hi,
I've always trusted CVS to do its work well, but today for the first time I
found out that it doesn't. The problem might not be in CVS itself, but it's
a very basic thing in CVS that does not work. The scenario is as follows:
- User A checks-out the latest version of project p.
- User B checks-out the latest version of project p.
- User A changes one of the files in p, and commits his changes to the
repository.
- User B changes one of the files in p (not the same file that user A
changed).
- User B commits his changes to p, without first updating his working copy.
Against all expectations, user B succeeds to commit even though his working
copy is not up to date, leading to an unstable latest version of the project
in the repository.
Technical details:
- User A works on Linux, using CVS client & server version 1.10.8.
- User B works on Windows 2000, using CVS client 1.10.7 and server 1.10.8
(both users using the same CVS server machine, same version of CVS on both
machines)
- The repository is on NFS.
Any idea?
Shlomo
- Commit inconsistency: Up-to-date check did not fail though it sho uld have !,
Reinstein, Shlomo <=
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Reinstein, Shlomo, 2003/02/18
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Reinstein, Shlomo, 2003/02/18
- Re: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Kaz Kylheku, 2003/02/18
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Reinstein, Shlomo, 2003/02/18
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Ludvig Borgne, 2003/02/19