Todd Denniston wrote: > assuming unix, > in proj_2_tree > | > |- dir1 > |- file1 softlink to ../proj_1_tree/file1 > |- dir2 > |- file2 softlink to ../proj_1_tree/file2 > |- file3 softlink to ../proj_1_tree/file3 > |- proj_1_tree > | > |- file1 > |- file2 > |- file3 Is "soft link" the same as a "symlink?" If they are different, then the rest of this message _might_ not apply.
If they are the same, then this is a Really Bad Idea. The problem is, CVS sees dir1/file1 and proj_1_tree/file1 as completely separate, independent files. If user A is checking into dir1, then CVS will not lock proj_1_tree. This means that user B can simultaneously check in changes into proj_1_tree - leading to... shall we say, all kinds of fun. Bottom line: symlinks, if used at all, should _only_ be used for directories, not for files. -- 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 Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
