Bug 221163 - [Patch] Drop patches on target files/folders/projects
Summary: [Patch] Drop patches on target files/folders/projects
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-03 10:58 EST by Tomasz Zarna CLA
Modified: 2019-09-06 15:31 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2008-03-03 10:58:43 EST
I'm working with patches which don't have patch root specified. Every time I want to apply such patch I need to manually select target resource, even though the target is in the same folder. 

It would be great if I could drag'n'drop the patch file on the target instead. At this moment dropping is an allegory for copying/moving a resource, but we could show a dialog asking him/her whether he/she wants to copy/move the resource or apply the patch (if it's a valid patch).

I believe we will need to introduce a content describer for patches in order to start with this.
Comment 1 Remy Suen CLA 2008-03-03 13:17:04 EST
Tomasz, I think you wrote a content describer already for patches in that bug requesting for a "Patch File Editor"?
Comment 2 Remy Suen CLA 2008-03-03 15:09:50 EST
I did a quick search, I was referring to attachment 80237 [details] from bug 190418.
Comment 3 Tomasz Zarna CLA 2008-03-04 04:21:22 EST
 (In reply to comment #1)
> Tomasz, I think you wrote a content describer already for patches in that bug
> requesting for a "Patch File Editor"?

That's is correct, but I think the patch for bug 190418 is more like a POC than a real fix (at least in its current shape). Nevertheless, it's a good place to start. Thanks for bringing that up Remy.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:31:09 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.