Paul Sander wrote:
> I can say from experience that assembling a sandbox from an unlocked
> repository is no more or less safe than any out-of-date sandbox, provided
> the CVS metadata are correct with respect to the contents of the working
> files. In either case, a "cvs update" is required (with the accompanying
> conflicts resolved) before a commit can be completed. This can be tricky
> if the read operation is done concurrently with a commit or tag operation.
>
> The first point, that the operation be read-only is absolutely correct.
> To resolve issues surrounding concurrent reads and writes, my method
> required that all revisions retrieved from the repository be identified
> in advance.
What of the case where a file is being written while a read-only CVS attempts
to read it. Providing RCS doesn't consistently break, and I'm far from sure
it will, the resulting partial file in the sandbox will have valid metadata.
If the file was touched in the sandbox, a later commit could check in
garbage.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] CollabNet ( http://collab.net )
--
I'm filling out the report right now. We haven't quite figured out if he
committed suicide or died trying to escape.
- Claude Rains as Captain Louis Renault, _Casablanca_
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
