Bug 92781 - [Repo View] Add Change Sets to remote compare
Summary: [Repo View] Add Change Sets to remote compare
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 102620 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-26 11:20 EDT by Eugene Kuleshov CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Kuleshov CLA 2005-04-26 11:20:41 EDT 
When you run comparison between current workspace and CVS tag/version the
results can be shown in synchronize view and you can also use "Change Set"
feature to get better groupping of the comparison results.

However if you open CVS Repositories view, select two versions/tags from there
and run "Compare" action it will show results in the editor and not in the
dialog  and not in the Synchronize view. As a result it does not provide
groupping by "Cahnge Set". Please add an option to use Synchronize view for
comparison between two CVS tags/versions.
Comment 1 Michael Valenta CLA 2005-04-26 11:30:54 EDT 
By design, the synchronize view shows the synchronization state between the 
local workspace and the server. The comparison you mention is between two 
remote trees. However, the nature of your request is still valid. You wish to 
have the ability to see change sets in the tree viewer that is shown in the 
remote compare editor.
Comment 2 Michael Valenta CLA 2005-07-05 09:07:28 EDT 
*** Bug 102620 has been marked as a duplicate of this bug. ***
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:27 EDT 
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.