Community
Participate
Working Groups
The synchronize view considers that the repository state is always better than the workspace. This could be wrong if someone has released a change, then you have no choice but accepting it then undo it manually and re- release the fixed version. This becomes really painfull, if the state you want to revert to is precisely an old one, which you have in your workspace. I would like to be able to release my old version instead of having the only option to catchup with the bogus new one. Currently, you have to manually add a space so as to create a conflict, but then a compare will also see this fake version, and this is causing more confusion. Why not simply allowing to release even if you think only catchup is expected ? Note that the same applies to outgoing changes which you might not want to preserve (you have to use "replace with stream contents". This one has a simpler solution, but again it is not very natural. The synchronization view could solve all these at once by simply allowing me to always catchup/release. Maybe if I am going against the stream, I should be prompted to confirm my action, but it should still be possible. NOTES:
PRODUCT VERSION: SDK 137
Michael is currently working on the improvements to the synchronize view that will allow us to do this. Moving to Michael.
You can now: - commit an incomming change - update outgoing changes In the first case, it creates a new revision with the contents of the base, which is the desired net effect. We can't help that it creates a new revision because in CVS you can't turn back the clock.
