Bug 259074 - "Apply Patch" ignore patch segments does not work correctly for new files
Summary: "Apply Patch" ignore patch segments does not work correctly for new files
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-17 04:24 EST by Christoph Hohmann CLA
Modified: 2019-09-06 15:35 EDT (History)
1 user (show)

See Also:

Attachments
Patch file with leading path name segments (157 bytes, text/plain)
2008-12-17 04:24 EST, Christoph Hohmann CLA 		no flags Details
Patch file without leading path name segments (151 bytes, text/plain)
2008-12-17 04:25 EST, Christoph Hohmann CLA 		no flags Details
View All 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 Christoph Hohmann CLA 2008-12-17 04:24:31 EST 
Created attachment 120672 [details]
Patch file with leading path name segments

Build ID: M20080911-1700

Steps To Reproduce:
A patch that is created using an external tool that does contain leading path name segments and new files can not be applied using the Apply Patch wizard.

1. Create an empty Project named "Project"
2. Open the Apply Patch wizard
3. Select the prefix.patch file
4. Select "apply the patch to the workspace root"
5. Set "Ignore leading path name segments" to 1

The wizard shows Project/new_file.txt with one failed hunk.

If you do the same with the noprefix.patch and "Ignore leading path name segments" set to 0 it also shows Project/new_file.txt but the hulk does not show as failed.


More information:
Comment 1 Christoph Hohmann CLA 2008-12-17 04:25:12 EST 
Created attachment 120673 [details]
Patch file without leading path name segments
Comment 2 Mike Wilson CLA 2009-05-05 12:34:36 EDT 
Changing Version tag to something more believable.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:35:10 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.