Reversing a file deletion and keeping history
Hello,
(Using RTC 6.0.2).
One of our developers deleted files from a component and the change set was delivered in the stream.
Now we would like these files to come back into the component.
If I do a reverse from my repository workspace, applying the patch will create new files and we'll lose the previous history.
Is there any way to get the files back with their history ?
Thanks for your help,
Regards,
Marie
Accepted answer
When you use the "reverse" operation, you will keep all the history ... you will see a delete in the history, followed by the version resulting from the reverse. (I have verified this in 6.0.5, but I don't believe this behavior has changed since 6.0.2).
Comments
showing 5 of 6
show 1 more comments
One other answer
Another way to do this is to do a "rollback".
1. Discard the change-sets from your history (the ones that delete the files)
2. Right-click the component (in pending changes) and select "Replace in <stream>". That will create a baseline and roll the stream to that baseline (the component without the change-sets that deletes the files).
3. After a rollback, make sure all developers accept the incoming "replace" or discard outgoing change-sets that they didn't create themselves.
This is a less "nice" operation than the one described above, but it is actually traceable in the most recent versions of RTC, because each stream now has an "Operations history", and you can actually rollback the rollback itself, if you decide it was not a good idea.
I would in most cases recommend the "reverse" option, because it is still rolling the stream "forward" and is traceable in history. But sometimes a rollback is necessary.
/Morten