[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

merging adjacent changes

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 22 Feb 2016 17:23:56 +0000

"Bert Huijben" <bert_at_qqmail.nl> writes:

> Personally I agree that I would like to see a text-conflict raised in
> this specific case where the change regions touch each other. But then
> there is that old discussion, ....

I added the test because we had already, perhaps inadvertently,
implemented the behaviour.

Back in 2003 we didn't have 'svn resolve' so resolving a text conflict
required the user to edit the file. Now we have 'svn resolved' which
may make resolving text conflicts easier. Perhaps that allows us to
change Subversion to create more conflicts?

We know merge is essentially imperfect or fuzzy, the question is where
to draw the line. Which, if any, of these cases should merge without
conflict and what should the merged result be?

1. common first second
    ancestor branch branch

    A A A
    B Bbr1 B
    C C Cbr2
    D D D

2. common first second
    ancestor branch branch

    A A A
    B Bbr1 B
    C new new
    D C C
                     D D

3. common first second
    ancestor branch branch

    A A A
    B Bbr1 B
    C new new
    D C Cbr2
                     D D

4. common first second
    ancestor branch branch

    A A A
    B Bbr1 B
    C newbr1 newbr2
    D C Cbr2
                     D D

There are probably more cases.

-- 
Philip Martin
WANdisco
Received on 2016-02-22 18:24:04 CET

This is an archived mail posted to the Subversion Dev mailing list.