Thread (17 messages) flat view 17 messages, 3 authors, 2016-06-15

Re: [PATCH 9/9] rerere forget path: forget recorded resolution

From: Johannes Sixt <hidden>
Date: 2016-06-15 22:47:58

Possibly related (same subject, not in this thread)

Junio C Hamano schrieb:
Johannes Sixt [off-list ref] writes:
quoted
When you simply call ll_merge(), will it obey any merge drivers that
are defined in .gitattributes? Do we care about them?

I already had an implementation of "rerere forget" before you
presented this solution, but it relies on that the user calls
"checkout --conflict=merge" first. One reason (besides its simplicity)
was that it does not have to care how the merge is computed.
Doesn't "checkout --conflict=merge" use the same ll_merge() machinery?
It does, without setting up .gitattributes, either (IIUC), which is a bug IMO.

That said, I consider your solution superior because it works without 
depending on conflict markers in the file in the worktree. Nevertheless, 
we should think about whether merge drivers of .gitattributes should be 
obeyed. I think they should: For example, a specialized XML merge driver 
could leave conflicts that are different from those that merge-recursive 
generates.

-- Hannes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help