Bug 68690 - [Patch] Create patch against filesystem
Summary: [Patch] Create patch against filesystem
Status: RESOLVED DUPLICATE of bug 71374
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 73632 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-26 09:43 EDT by Noel Grandin CLA
Modified: 2007-10-24 12:27 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Noel Grandin CLA 2004-06-26 09:43:25 EDT
Use Case: I often work on open-source projects where I download a zip file of 
the project source.

When I want to create a patch to send back to the project, I have to use a 
command version of diff.

I want to be able to tell eclipse : create me a patch in this project, using 
the following zip file/directory location as the unmodified version.
Comment 1 Michael Valenta CLA 2004-06-28 09:23:25 EDT
Moving to Platform Compare as this is the component that provides client based 
diffing inside Eclipse.
Comment 2 Ed Burnette CLA 2004-09-01 13:24:39 EDT
I could use this too. Here's the use case. I'm working with some source using 
a beta Perforce team provider (the WSAD one from perforce.com), which doesn't 
have a Create patch feature like the CVS provider does. Nevertheless I need to 
be able to diff my changes against the source copied from Perforce and send 
the developer a patch. Currently I just send them whole copies of files I've 
modified but obviously a patch format would be much more convenient.

It's curious that Apply Patch is generic and available no matter what team 
provider you're using but Create Patch is not. I know that the reason is that 
CVS provides a diff command that the CVS provider is using, but that doesn't 
help the other providers, or someone not using a team provider at all.
Comment 3 Ingo Muschenetz CLA 2006-10-26 09:07:57 EDT
(In reply to comment #2)
> I could use this too. Here's the use case. I'm working with some source using 
> a beta Perforce team provider (the WSAD one from perforce.com), which doesn't 
> have a Create patch feature like the CVS provider does. Nevertheless I need to 
> be able to diff my changes against the source copied from Perforce and send 
> the developer a patch.

For those interested in trying to get Perforce to update the WSAD team provider with a "Create Patch" functionality, there is a reference number of "CALL#1456122" which you can encourage support for. However, universal support would be great.
Comment 4 Michael Valenta CLA 2007-06-22 09:02:04 EDT

*** This bug has been marked as a duplicate of bug 71374 ***
Comment 5 Tomasz Zarna CLA 2007-10-24 12:27:28 EDT
*** Bug 73632 has been marked as a duplicate of this bug. ***