Bug 104366 - [History View] Create Patch between two file revisions
Summary: [History View] Create Patch between two file revisions
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
: 172725 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-07-19 12:06 EDT by rasto CLA
Modified: 2019-09-06 16:03 EDT (History)
5 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 rasto CLA 2005-07-19 12:06:16 EDT 
I didn't find one important feature in Team issue.
I would like to create patch between 2 cvs versions of my File.
How is that possible? Can it be added in Eclipse CVS Features?
Otherwise I have to use cvs diff .. -r...

Thanks
Comment 1 Michael Valenta CLA 2005-07-19 12:13:43 EDT 
Eclipse does not currently provide this funtionality. This is related to bug 
21383 but I'll keep it separate since you mentioned a specific file. (i.e. bug 
21383 is specific to the repo view whereas a patch for a single file revision 
could be done in the history view).
Comment 2 rasto CLA 2007-01-23 03:02:46 EST 
Feel free to mark this bug as duplicate of those mentioned. It's the same issue, the file I meant, is just commited version of file..
Comment 3 Michael Valenta CLA 2007-02-05 08:39:58 EST 
*** Bug 172725 has been marked as a duplicate of this bug. ***
Comment 4 Mauro Molinari CLA 2008-11-10 06:27:22 EST 
Shouldn't this be covered by bug #71374?

Mauro.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:03:28 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.