Bug 113629 - [History View] CVS-History for packages
Summary: [History View] CVS-History for packages
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P5 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 114479 128599 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-10-25 02:03 EDT by Georg Sendt CLA
Modified: 2019-09-06 15:30 EDT (History)
6 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 Georg Sendt CLA 2005-10-25 02:03:12 EDT 
Allow CVS-History not only for files but also for packages (and packages trees).
This would give one a better overview about CVS changes.
Comment 1 Michael Valenta CLA 2005-11-02 14:58:41 EST 
*** Bug 114479 has been marked as a duplicate of this bug. ***
Comment 2 Eugene Kuleshov CLA 2006-08-07 17:00:56 EDT 
There is an Eclipse CVS changelog plugin released under CPL. http://cvschangelog.sourceforge.net/
It would be really nice if it would be integrated with core product.
Comment 3 Luca Azzalini CLA 2006-10-27 10:52:59 EDT 
Please fix this!
The suggested workaround (http://cvschangelog.sourceforge.net/) doesn't work for me (I get an "internal", no more specific error, on eclipse 3.1.2).
And it doesn't show tags (as I can see from the screenshot).
Comment 4 Michael Valenta CLA 2006-10-27 11:02:08 EDT 
Unfortunately, we don't have the cycles to address this issue. If it really matters to you, perhaps you should consider supplying a patch.
Comment 5 Matthias Bohlen CLA 2007-08-02 17:14:34 EDT 
*** Bug 128599 has been marked as a duplicate of this bug. ***
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:30:07 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.