Bug 110905 - [Sync View] Ignore differences caused only by CVS keyword update
Summary: [Sync View] Ignore differences caused only by CVS keyword update
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted, investigate
Depends on:
Blocks:
 
Reported: 2005-09-28 03:02 EDT by Will Hains CLA
Modified: 2019-09-06 16:15 EDT (History)
1 user (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 Will Hains CLA 2005-09-28 03:02:46 EDT 
When using the CVS compare editor to diff a file that includes CVS keywords 
(eg. $Id$, $Revision$, etc.), it would be better to be able to ignore changes 
to lines that only changed because CVS updated the keyword. That way the only 
changes you would see would be the changes actually made by the last person to 
commit the file.
Comment 1 Michael Valenta CLA 2005-09-28 08:54:39 EDT 
The problem is that CVS makes use of plugged-in compare viewers to show a 
comparison. We would either needs API to communicate to the viewer that some 
part of the comparison needs to be delegated to CVS or we would need to modify 
the input to the compare viewer to normalize the keyword substitutions. The 
later approach is complicated by the fact that the compare editor can also be 
used to make changes to the local copy. Another option is to support keyword 
substitution changes for individual files during comparisons but this has it's 
own complications.
Comment 2 Michael Valenta CLA 2006-06-19 15:59:11 EDT 
Investigate for 3.3.
Comment 3 Michael Valenta CLA 2006-08-17 11:10:36 EDT 
There is currently no plan to address this issue.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:15:41 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.