Bugzilla – Full Text Bug Listing
| Summary: | [client] Add Save Patch action | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Tomasz Zarna <tomasz.zarna> |
| Component: | Git | Assignee: | Tomasz Zarna <tomasz.zarna> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw |
| Version: | 0.3 | ||
| Target Milestone: | 0.4 M2 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 367081 | ||
| Bug Blocks: | 361425 | ||
|
Description
Tomasz Zarna
Is this an action to save the patched file(original file + diff) or just the unified diff ? Lets confirm the work flow if it is the first case. Here is my assumption: 1.take action on "apply patch" for a file. (will this action be invoked from navigator?) 2.select the patch file from where ever you stored it, or just paste the patch. 3.The compare editor opens up and show as preview. 4.In the compare editor, save the patched file. (In reply to comment #1) > Is this an action to save the patched file(original file + diff) or just the > unified diff ? I was thinking about saving the diff. > 1.take action on "apply patch" for a file. (will this action be invoked from > navigator?) See bug 365575, comment 0. My initial idea was to add the action to the Repos page, but drag'n'droppin' a patch on the Git Status page makes sense to me as well. Would you like to see it somewhere else? I said drag'n'drop but the first cut will probably look similar to the "Import from ZIP" action when you browse your files looking for the patch. Fixed with 309cbd3a9b7c6e0d3edd0d8010cbbf651d3dbeb2 . |