Re: theirs/ours was Re: [PATCH 6/6] Add a new test for using a custom merge strategy

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: theirs/ours was Re: [PATCH 6/6] Add a new test for using a custom merge strategy

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:45:04

Johannes Schindelin [off-list ref] writes:
Well, I have to say that the workflow is a bit backwards if the person who 
_publishes_ the thing is the one saying "Ooops, my version no goodie, 
other version please, but so that pull still works".

I would have expected the one who has the good version to make the choice.
That reminds me of:

    http://thread.gmane.org/gmane.comp.version-control.git/89178

to one of whose messages I sent a response today.

Re: theirs/ours was Re: [PATCH 6/6] Add a new test for using a custom merge strategy

From: Sverre Rabbelier <hidden>
Date: 2016-06-15 22:45:04

On Mon, Jul 28, 2008 at 22:07, Junio C Hamano [off-list ref] wrote:
That reminds me of:

   http://thread.gmane.org/gmane.comp.version-control.git/89178

to one of whose messages I sent a response today.
Mhhh, but the proposed strategy there was in response to the 'insane'
git-merge-theirs version, not to the 'exact opposite of
git-merge-ours' that I refer to now, yes? Do you have any particular
feelings wrt to that?

-- 
Cheers,

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