Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 11426

Summary: [CVS Sync View] Sync view should show version creator and comment
Product: [Eclipse Project] Platform Reporter: Nick Edgar <n.a.edgar>
Component: TeamAssignee: Platform-VCM-Inbox <platform-vcm-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: enhancement    
Priority: P3 CC: dj.houghton, ggregory, henning.boeger, hudsonr, Michael.Valenta, philippe_mulet, preuss
Version: 2.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on: 23825    
Bug Blocks:    

Description Nick Edgar CLA 2002-03-14 20:24:06 EST
Build 20020314

It would be very helpful if the sync view could show who created a version and 
the corresponding comment.
This could be put in a small pane at the bottom of the view, or even in the 
status line, when an incoming change or addition is selected.

It would help if this could be shown for incoming deletions as well (i.e. who 
deleted the file).
Comment 1 Kevin McGuire CLA 2002-03-18 15:08:18 EST
May be a duplicate PR - I remember James+I discussing this.
Comment 2 Kevin McGuire CLA 2002-05-17 20:32:35 EDT
*** Bug 10475 has been marked as a duplicate of this bug. ***
Comment 3 Michael Valenta CLA 2002-08-23 09:24:44 EDT
The author/creator is now displayed. The comment is not yet.
Comment 4 Michael Valenta CLA 2002-09-24 13:35:29 EDT
*** Bug 23921 has been marked as a duplicate of this bug. ***
Comment 5 Michael Valenta CLA 2002-09-24 13:36:47 EDT
Bug 23825 suggests feeding the history view with the comment. This would be  
good start.
Comment 6 Sonia Dimitrov CLA 2002-11-18 10:34:47 EST
*** Bug 26403 has been marked as a duplicate of this bug. ***
Comment 7 Sonia Dimitrov CLA 2002-11-19 09:49:44 EST
*** Bug 26649 has been marked as a duplicate of this bug. ***
Comment 8 Sonia Dimitrov CLA 2002-12-19 16:39:55 EST
*** Bug 28686 has been marked as a duplicate of this bug. ***
Comment 9 Randy Hudson CLA 2002-12-20 10:14:40 EST
If the Synchronize View is a fast view, then opening the Release History from it
(besides being expensive) collapses the synchronize view.
Comment 10 Jean-Michel Lemieux CLA 2003-06-16 15:13:19 EDT
*** Bug 38416 has been marked as a duplicate of this bug. ***
Comment 11 Randy Hudson CLA 2003-07-15 10:07:45 EDT
Please note that showing the release comment in the tabletree is preferred to 
showing it only after opening using double-click.

It sounds like this is the plan and that it is almost finished.  Great!  Bug 
38416 mentions the latency issue associated with showing release comments only 
after the user has double-clicked to open the file.
Comment 12 Jean-Michel Lemieux CLA 2003-07-23 15:08:13 EDT
There are other plan items that we have to start in M3, deferring for now.
Sorry. currently usernale and comment is shown in the compare view. Also, we are
waiting for an improved tabletree from SWT.
Comment 13 Jean-Michel Lemieux CLA 2003-09-16 21:48:33 EDT
We removed the username + comment for the base/remote revisions that we had
added to the Compare editors opened from the new sync view. It added too much
overhead to open a compare editor.

Instead, the CVS History view now supports linking with the active editor.

Keeping this open to investigate showing this information in the sync view
instead. But we are currently waiting for a better tabletree widget.
Comment 14 Jean-Michel Lemieux CLA 2003-11-04 20:33:02 EST
*** Bug 46067 has been marked as a duplicate of this bug. ***
Comment 15 Jean-Michel Lemieux CLA 2004-06-11 16:49:22 EDT
Post 3.0
Comment 16 Michael Valenta CLA 2004-11-08 21:49:03 EST
Change sets allow the username and comment to appear in the sync view
Comment 17 Randy Hudson CLA 2004-11-09 10:33:08 EST
Why is the resolution "WorksForMe"?  If new function was added in 3.1, then 
this is either closed or a duplicate of the new function, no?
Comment 18 Michael Valenta CLA 2004-11-09 10:58:01 EST
Technically you are correct. However, commit sets were added in 3.0 without an 
accompanying feature request so there is no bug to mark this a duplicate of.