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'm having a problem with the edit/commit/unedit sequence (and possibly the edit/update/unedit sequence). Quite often (but it seems not always) the following happens: - I do an edit on a file - I modify it and commit it (or I don't modify it, but an update modifies it) - On a subsequent unedit I get the message that the file has been modified and it asks me whether I want to revert. If I revert, it gets reverted to a previous revision and I need to update the file to get the HEAD revision (that I committed immediately before the unedit, or that I already got through the update preceding the unedit). If I don't revert, the file doesn't get unedited (at least not in the sandbox). An additional edit after the commit or update cleans that up and allows me to unedit without problems. This looks like cvsnt wouldn't keep track of the local backup copies properly on commit or update and still think that the outdated local backup copy is valid -- even after a commit (or update). Am I doing something wrong? This is cvsnt 2.0.34 on the server, and 2.0.41a through Tortoise on the client. I think this started to happen at a certain point (that is, cvsnt version), but I'm not sure when exactly. I didn't consciously track the cvsnt revisions bundled with Tortoise. Thanks, Gerhard