Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 221582

Summary:	[Patch] "Ignore leading path name segments" does not update
Product:	[Eclipse Project] Platform	Reporter:	Kane Bonnette <kane.bonnette>
Component:	Compare	Assignee:	Platform-Compare-Inbox <platform-compare-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	ralf
Version:	3.3.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Kane Bonnette

2008-03-05 15:30:15 EST

Build ID: M20071023-1652

Steps To Reproduce:
1. Team->Apply Patch
2. Select a patch file, click next
3. Select a project, click next
4. Choose a nonzero number of path segments to remove
5. Click Back Button twice
6. Choose new patch and project
7. Note that when the 3rd page is displayed, the number of segments indicated in the dropdown does not affect the number of segments ignored.


More information:
This is really only a problem if a user is comparing multiple patches to multiple projects, but not committing any of them.

Comment 1 Tomasz Zarna

2008-03-06 08:20:28 EST

I think that "Ignore path segments", "Reverse patch" and the fuzz factor option can be reset every time the user re-enters the "Review Patch" page. I'm not so sure if we can get away with reseting the others (ie "Show matched hunks", "Show excluded", "Generate .rej files"). On the other hand I think we should treat all of them equally. The other thing is that we could reset some of them iff the user changes the patch input (clicks "Back" button twice and changes the selection). What's your opinion?

Comment 2 Eclipse Webmaster

2019-09-06 15:30:14 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.

Comment 3 Eclipse Genie

2022-02-09 09:57:27 EST

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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.