How can I revert repository workspace back in time?
4 answers
- The pending changes always shows the difference between the repository workspace and the streams current state
- If you discard a change set in a workspace, but it is still in the stream you flow to, you see it as incoming
- I haven't tried suspending changes that are still incoming - have to try that once
If you want to bring a workspace into a certain state, you can
- Rebase to a snapshot
- Rebase single components to a baseline
If you have data on a stream that you want on top of that workspace state, you can accept it in.
Comments
Hi Ralph,
The pending changes always shows the difference between the repository workspace and the streams current state.
The Pending Changes view is not showing all changes that are listed in the component's history but that I have discarded from my workspace. It is only showing discarded changesets that were created after the initial baseline.
If you want to bring a workspace into a certain state, you can
- Rebase to a snapshot
- Rebase single components to a baseline
The pending changes DOES show the difference of its state and the state of the stream. If you discard from the workspace, the data is not there any more. If it is still in the stream, you get it as incoming.
You could revert the change, get a patch and deliver that to revert the change on the stream.
The initial baseline shows, as far as I know the initial state of the object. There is noting in there before that.
The CVS import is a bit tricky, can you look at the history of a stream that has the imported components on it? Do you see baselines? There is a good article about the import and you have to play with it a bit to get it right and especially to get the baselines imported.
For some reason when I discard changests from the CVS import, they don't show up in Incoming. They just disappear.
The CVS import was done about 2 years ago, so it's too late for me to go back and redo it. I need to work with what I've got.
I might be able to achieve what I need to by using Suspend instead of Discard.
Comments
What is strange about my case is that the initial baseline is dated in 2013. However, the repo has history from years prior to 2013 as it was migrated from CVS.
Suspending the changesets from the history view works. It's just surprising that discarding the changesets doesn't work.
Performing a "suspend" should be identical to performing a "discard", except that in addition to discarding the change set, the change set is also added to the "suspended" list. If that is not what you are seeing, then it sounds like a bug to me, and should be reported. If you'd like to screen share sometime next week, so I can take a look, just let me know.
Comments
Lauren Hayward Schaefer
JAZZ DEVELOPER May 19 '15, 7:23 a.m.I tried discarding changesets from my workspace as described in https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.scm.doc/topics/t_discarding_change_set.html&scope=null. The changesets created after the team started using RTC appear in my Incoming changes. However, the changesets created by converting from the CVS repo's history are not appearing in Incoming changes. Does the Pending Changes view only display changesets created after the first baseline?
Lauren Hayward Schaefer
JAZZ DEVELOPER May 19 '15, 7:36 a.m.Update: I can suspend the changesets that were created by converting from the CVS repo's history and they are listed in the Pending Changes view under suspended. Any ideas why RTC would know how to suspend but not discard these changes?