an [mailto:[EMAIL PROTECTED]
Sent: Monday, March 03, 2003 8:46 PM
To: [EMAIL PROTECTED]
Subject: Re: FW: Commit inconsistency: Up-to-date check did not fail though
it should have !
On Mon, Feb 24, 2003 at 03:36:58PM +0200, Reinstein, Shlomo wrote:
> I have also looked up the sources of CVS
Reinstein, Shlomo writes:
>
> What's wrong with the repository being on NFS? Isn't that the case with most
> CVS repositories? I didn't know there can be problems between an NFS client
> and server being on different platforms, but I bet that the machine on which
> the repository is located is als
lto:[EMAIL PROTECTED]]
Sent: Tuesday, February 18, 2003 5:38 PM
To: Reinstein, Shlomo
Cc: [EMAIL PROTECTED]
Subject: Re: Commit inconsistency: Up-to-date check did not fail though it
sho
Reinstein, Shlomo writes:
>
> - User A checks-out the latest version of project p.
> - User B ch
Reinstein, Shlomo writes:
>
> - 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
>
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 check
