Re: git gui: merge conflict display is misleading since it hides non-conflicting remote hunks [edit]

From: Jon Seymour <hidden>
Date: 2016-06-15 22:48:30

| changed conflict --> __change___
As a result, the user thinks that the only __change__ is the import
statement, and elects to resolve the commit in favour of the local
commit. This is the wrong thing to do because the remote hunk is then
lost to the history.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help