oldWing Posted March 8, 2011 Report Share Posted March 8, 2011 Started evaluating Plastic SCM and, as a "hermit developer", would like to use the modify-commit methodology. I unchecked the preference for "'Update' and 'Checkin' operations set files as read-only" option. It didn't appear to have an effect on my existing workspace, so I created a new workspace and test file. The new directory has the "Read-only (Only applies to files in folder)" property checked. When I hand the test file off to Plastic SCM with "Add to source control" the file is marked read-only. What am I missing? I did catch that the dialog box opened by clicking on "Preferences" is titled "Options". Thanks, Seth Plastic SCM 3.0.187.18 on Windows 7 Professional 64-bit. Survivor of DEC/CMS and StarTeam. Link to comment Share on other sites More sharing options...
psantosl Posted March 9, 2011 Report Share Posted March 9, 2011 Hi, Once you change this setting, you've to update your workspace so that your "readonly" files are changed to "writable". You can also "overwrite files", of course, if your editor allows that. To "change the readonly": go to the root of the workspace and run "update forced". Then use the "pending changes" view to find the files you've modified. Remember to check "find private" to locate new files, and also remember to configure the ignored files. pablo Link to comment Share on other sites More sharing options...
oldWing Posted March 9, 2011 Author Report Share Posted March 9, 2011 Pablo, Thanks, that does it! The documentation on "Update forced" is a little brief. Perhaps the documentation team will flesh it out a bit. Seth Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.