| Summary: | [server] Support for 3-way compare after merge happens. | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | libing wang <libingw> |
| Component: | Git | Assignee: | Project Inbox <orion.git-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bokowski, evan_hughes, Szymon.Brandys |
| Version: | 0.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 344286 | ||
|
Description
libing wang
(In reply to comment #0) > Server will add additional information in the response(e.g. common ancestor URI) Included in the response as "Base". I've tested it briefly, test cases also cover only simple scenarios but the new URI should work. See http://git.eclipse.org/c/e4/org.eclipse.orion.server.git/commit/?id=e7faf09c930b89fc0f47f7acceb8694c20fe46c8. Leaving the bug open in case we decide to add something more to the response. If now server returns old ,base and new . We may want diff uris liek , "old VS new" and "new VS base" , in addition to the existing "new VS old". I thought it over about the common ancestor sitting in the middle and asked around. Seems like having this UI will not help much. But indeed from server API , we need "old VS new" and "new VS base" , in addition to the existing "new VS old". We will figure out a better way how to bring up these diffs , maybe in separate pages if user needs it. According to http://wiki.eclipse.org/Orion/Milestone_Plan it has been deferred. (In reply to comment #3) > But indeed from server API , we need "old VS > new" and "new VS base" , in addition to the existing "new VS old". Libing, do you still need these? Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |