Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 26403 - Synchronize pane Compare pane should display commit comment
Summary: Synchronize pane Compare pane should display commit comment
Status: RESOLVED DUPLICATE of bug 11426
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-VCM-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-14 14:40 EST by Gary Gregory CLA
Modified: 2002-11-18 10:34 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Gregory CLA 2002-11-14 14:40:53 EST
When I do a Team CVS Synchronise and double click on a .java file, I get a very 
nice comparison pane. The version and author are displayed for both the local 
and incoming files but not the commit COMMNENT. This is especially important 
for the /incomming/ file.

I am not sure where the best place to add this would be.

(1) An resizable scrollable text area below the author and version static text 
area?
(2) A one line static text area below the author and version static text area 
that displays. The whole comment could be displayed as hint text when hovered 
on?

(Build id: 200211051258)

Thank you for considering this request,
Gary
Comment 1 Kevin McGuire CLA 2002-11-14 17:28:42 EST
>>The whole comment could be displayed as hint text when hovered 
on?

We actually tried this during 2.0 but ran into problems because we need to go 
to the server to get the comment, and hover help is just a bad place to do long 
operations.  Unfortunately we then ran out of time, but also had never figured 
out then the best place to show it.

We may still have a bug report open on this subject of seeing the commit 
comment. I agree its important.
Comment 2 Sonia Dimitrov CLA 2002-11-18 10:34:46 EST

*** This bug has been marked as a duplicate of 11426 ***