Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Hello, I think that this used to be different. Now it works like this: 1- Edit a directory. 2- Modify some files. 3- Commit the directory. Only the modified files get committed, their "edit" flag gets cleared, their revision number gets incremented. 4- Unedit the directory, to remove the edit flag from the files that didn't get committed. Step 4 is where the weird thing happens: the files committed in step 3 get reverted to the revision prior to the commit. Since in step 4 they shouldn't have their edit flag set, they shouldn't get unedited -- IMO. Am I doing/seeing something wrong here? (BTW, this "works" also with single files, of course. An unedit after an edit/modify/commit sequence reverts the file to the revision prior to the commit.) The workaround I'm using is to update after every unedit. And to unedit after every commit. But that's a bit cumbersome, and also error-prone. p:\gerhard>cvs ver Client: Concurrent Versions System (CVSNT) 2.5.02 (Servalan) Build 2064 (client/server) Server: Concurrent Versions System (CVSNT) 2.0.34 (client/server) Thanks, Gerhard