How to move back to older code version in scm in Eclipse client?
Hi all,
We are developing a small project in RTC. One of my colleagues has delivered recently the code (several changesets) which we do not want to release in current version.
Therefore I would like to move back to the point in the time when the code was ready to release, make some tests and create an snapshot of that code.
Anyway I have couple of problems e.g. how to move back to that version in the code and how to create snapshot of that version.
What is the best recommendation here?
We are developing a small project in RTC. One of my colleagues has delivered recently the code (several changesets) which we do not want to release in current version.
Therefore I would like to move back to the point in the time when the code was ready to release, make some tests and create an snapshot of that code.
Anyway I have couple of problems e.g. how to move back to that version in the code and how to create snapshot of that version.
What is the best recommendation here?
Accepted answer
See How do I remove a change set from a stream? in the Source Control FAQ.
Comments
1 vote
1 vote
One other answer
Krzysztof,
depending on the last time you did a snapshot before the "offending" change sets were delivered, this alternative approach might get you around patches:
Create a workspace from the latest snapshot. Flow that workspace to the stream containing the "offending" change sets. Accept only the change sets you want to the workspace, except the ones that should not be in there. Now make a snapshot in workspace and promote to stream, rebase to that snapshot.
Would that work?
Depending on how the change sets are intertwined you might need 4.0.6 and beyond for Merge Gap handling.
- Arne
depending on the last time you did a snapshot before the "offending" change sets were delivered, this alternative approach might get you around patches:
Create a workspace from the latest snapshot. Flow that workspace to the stream containing the "offending" change sets. Accept only the change sets you want to the workspace, except the ones that should not be in there. Now make a snapshot in workspace and promote to stream, rebase to that snapshot.
Would that work?
Depending on how the change sets are intertwined you might need 4.0.6 and beyond for Merge Gap handling.
- Arne
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Mar 11 '14, 7:56 a.m.1 vote
Krzysztof Kaźmierczyk
Mar 11 '14, 9:21 a.m.Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Mar 11 '14, 9:33 a.m.Alex Fitzpatrick
JAZZ DEVELOPER Mar 11 '14, 2:31 p.m.