Thread (11 messages) flat view 11 messages, 5 authors, 2016-06-15

Re: more merge strategies : feature request

From: Nanako Shiraishi <hidden>
Date: 2016-06-15 22:45:43

Quoting "Leo Razoumov" [off-list ref]:
On 12/2/08, Caleb Cushing [off-list ref] wrote:
quoted
quoted
I guess that "no-overwrite" can be achieved by
 >
 >  git merge -s ours --no-commit

no it doesn't. which is why I called it a bad name. no-overwrite would
 still add new lines to the file not in ours (and no-commit isn't
 needed in that case) it just wouldn't overwrite conflicting lines, my
 understanding of ours is that it will keep the files as is.
Isn't what Caleb wants "-X ours/theirs" per-hunk option for merge strategy backends?

It was discussed several months ago on the list and was rejected.  For details you can start here:

    http://thread.gmane.org/gmane.comp.version-control.git/89010/focus=89021

I still think the patch in the above link was reasonable, but the thread was distracted into discussing minor syntactical details of how the option gets passed to the backend, and the rest of the discussion to decide if it makes sense to add such a feature was unfortunately lost in the noise and never concluded.

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help