| Summary: | Tracking code changes to Platform | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Sam Fuqua <sfuqua> | ||||
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, hsoliwal, john.arthorne, remy.suen | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Sam Fuqua
Created attachment 184617 [details]
This zip contains code changes to JFace
For what are those code changes? It looks like publishing a change of org.eclipse.jface.window.Window (a minor change) to meet EPL requirements. PW (In reply to comment #3) > It looks like publishing a change of org.eclipse.jface.window.Window (a minor > change) to meet EPL requirements. Yes, I see that. But it would be nice to give some explanations along with the changes and of course we'd prefer to have a patch containing the changes instead of the changed source file. Without any description of the bug or the attachment itself, this has little meaning, let alone calling it a bug or enhancement.Please try to mention what is it that the attachment tries to accomplish or fix. For Documentation Window Menu: -> Help -> Help Contents ->Workbench User Guide > Tasks> Working in the team environment with CVS> Working with patches I am marking it as INVALID until further information is provided. |