Summary: | [Doc] fuzz factor description wrong/inconsistent with actual patch definition | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Joseph P. Skudlarek <JskudEcl> | ||||
Component: | Compare | Assignee: | Tomasz Zarna <tomasz.zarna> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | mober.at+eclipse, Szymon.Brandys, tomasz.zarna | ||||
Version: | 3.1 | Keywords: | Documentation | ||||
Target Milestone: | 3.4 RC4 | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | hasPatch | ||||||
Attachments: |
|
Description
Joseph P. Skudlarek
2005-11-12 11:37:51 EST
Thanks. We'll update the doc before 3.2 ships. Fixed The description from the Workbench User Guide still uses term of "location" which is inadequate to how the fuzz factor actually works. Moreover, as pointed in bug 131574, comment 7, "Maximum fuzz factor" is no longer a proper name for the field on the Apply Patch wizard. I assume that this has been reopened... would it make sense to update the target milestone to avoid confusion? (In reply to comment #4) > would it make sense to update the target milestone to avoid confusion? Sorry, my fault. Created attachment 103314 [details]
Updated "Working with patches" section
Applied to CVS HEAD with some minor modifications. Verified in I20080613-2000. |