Community
Participate
Working Groups
Build ID: M20071023-1652 Steps To Reproduce: 1. do a "Replace With > Revision..." on a single resource 2. the resource changes, this can be seen in the resource history 3. the resource is NOT marked dirty, so it is not possible to commit More information: I would expect the resource to be dirty in order to commit it (going back to a previous revision). Currently I have to change something (a space or newline) to get a conflict in the synchronize view and then do a "Override and Commit".
Done. Fix should be available at the end of this week.
Thank you for the quick implementation. I have thought about this feature a little bit. Maybe this should be configurable, for example in the dialog with a check box: "[ ] Mark replaced files dirty" or in the preferences as a general setting. I think this can be in some cases not the desired behavior. I cannot check how CVS this handles, because I have only SVN at work. Maybe the default behavior should be the same as CVS.
In next build this functionality will works like in CVS: 1) "Replace with Latest Revision" performs revert and updates content to the head of repository 2) "Replace with URL/Revision" exports content from repository in order to enable future commits. Also you can update to oldest revision by calling "Upadte To" action from the History View or by performing "Switch To" action from Team menu. So, I think the option will be redundant in that case.
