Community
Participate
Working Groups
This is the case: - I have a resource (a java file) managed by a cvs repo - I can see some remote versions of that file in the history - I want to select one of the remote revisions and see the change set in the navigator - by the change set I mean all files that were part of the same commit
The other way of getting a similar result would be to enable Filters to use CVS based information like comments or user names. I could also imagine creating a Working Set similar way. Of course, both of them would be long-running operations. We would need to check all shared resources from a workspace, fetch their revisions and look for a one that match given criteria.
The problem with this specific request is that it would require additional support from the server to do it efficiently. What you ask is possible in 3.3 in a round about way by selecting one or more projects (or resources) and comparing what you have locally with a tag the pre-dates the commit you are interested in. You can then put the synchronize view into Change Set mode and find the Change set of interest. Yiu can then select the change set and pick the Compare Change Set (that's not the exact name of the action but it is something similar) to see all the changes in a compare editor. It would be possible to come up with a way to launch this from the History view but it would be fairly long running and would need to prompt the user for the projects to be searched.
I think that this request is reasonable then. I will mark it ASSIGN with low priority and I will pick it up when I have more free time. Anyway an external contribution is well seen.
I believe that addressing bug 32455 could help solving this one as well.
The same with newly added bug 204776.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
