[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Commit inconsistency: Up-to-date check did not fail though it
|
From: |
Larry Jones |
|
Subject: |
Re: Commit inconsistency: Up-to-date check did not fail though it |
|
Date: |
Tue, 18 Feb 2003 14:13:39 -0500 (EST) |
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 also a Linux machine.
It's been discussed here extensively in the past. The executive summary
is that there have been lots of reports of repository corruption caused
by interoperability bugs between different NFS implementations, so
you're advised to put your CVS repository on a locally mounted disk.
-Larry Jones
Why can't I ever build character in a Miami condo or a casino somewhere?
-- Calvin
- 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 !, 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
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Fabian Cenedese, 2003/02/19
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Reinstein, Shlomo, 2003/02/23
- RE: Commit inconsistency: Up-to-date check did not fail though it sho uld have !, Reinstein, Shlomo, 2003/02/23