Replies: 2 comments 1 reply
-
I don't think the headers from the unified diff format add much. The line numbers are not needed for finding the right location because the hunk is already in the right place, and the labels don't provide any information that isn't easy to find by looking above the conflict hunk. Regarding binary files, you should be able to configure your tool as a custom merge tool for
That might make sense. My main concern is that it implies a seemingly arbitrary threshold. #823 is also related. |
Beta Was this translation helpful? Give feedback.
-
Are you thinking of humans or algorithms? |
Beta Was this translation helpful? Give feedback.
-
I had forgotten after posting the following proposal from git-branchless.
I recently remind it.
I'm not sure if it's a valid proposal in this project, but I'm curious about your opinion.
1. Snapshot and diff
My opinion is to use snapshot if there are many changes and diff if there are few.
Also, for diff, let's mark it as Unified Format.
I think it's more consistent, although it's slightly changed from the original proposal.
Diff and Snapshot
Snapshot and Diff
Diff and Diff style
2. Binary
In the case of a conflict of the binary, I personally use a simple tool to generate
base
andtheir
files.Beta Was this translation helpful? Give feedback.
All reactions