Thread (1 message) 1 message, 1 author, 2020-07-21

Re: Request for adding a "clean" merge strategy for a double-commit merge to deal with conflicts separately

From: Junio C Hamano <hidden>
Date: 2020-07-21 20:43:55

Elijah Newren [off-list ref] writes:
I disagree that they are "lost".  Rather, git doesn't make them very
easy to access: git log -p won't show you any output for a merge by
default, and the only options that exist (-c, -cc) don't do what you
need to see how conflicts were resolved.
With "sometimes" sprinkled into appropriate places, you are 110%
right.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help