Colm Aengus Murphy wrote: > We've come across the following funny when using the cvs > editors feature. > In my workspace I do a "cvs edit" to indicate I am editing a file. > "cvs editors" correctly reports me as an editor. > If I then create another workspace using "cvs co" and run > "cvs editors" > I am no longer listed as an editor of the file. Darren Bowles submitted a patch to correct this, on the bug-cvs list, two days ago. Is this a good demonstration of statistical clustering, or what? :=)
> Another funny is that you can only be listed as an editor of > a file once > even though you might be editing the same file in more than > one workspace. Well, this one's a bit trickier. The repository does not keep track of how many locations you have a workspace checked out (except _maybe_ in the history file). Seems to me keeping track of which locations you're editing and which you aren't would be an administrative nightmare, getting into situations that could be extremely difficult to correct. For example, suppose a user checks out a project, issues 'cvs edit' on one or more files, then abandons the changes by simply deleting the working copy. In order to release the edit, the user would have to re-create the exact same directory structure, then issue the 'cvs unedit' command. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) _______________________________________________ Info-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/info-cvs
