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

Re: Resolving Conflicts

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 25 Oct 2013 19:47:12 +0200

On 25.10.2013 13:14, Avinash Singh wrote:
> Hi,
> I have experienced an issue in the way conflicts are resolved.
> Basically I had a conflicted file which had no conflicts within the
> file. Everything looked to be merged correctly. So I right-clicked the
> “red” file from the “check for modifications” screen and selected the
> “Resolved” option.
> This however caused some merge information to be part of the file. For
> example:
> <<<<<<< .working
> >>>>>>> .merge-right.r13749
> I redid the merge and selected “Edit Conflict”. In the new window I
> selected “Mark as Resolved”, this merged the file correctly.
> Why do both these options have different behaviour?

My guess is that you have the diff viewer/conflict editor
(TortoiseMerge?) configured to ignore EOLs. But when you did the merge,
you forgot to specify to ignore EOLs/whitespace changes. So you got a
conflict due to different EOLs.
Then you opened the conflicted files in the editor which ignores EOLs
and then there's no conflict (the conflict is in EOLs, but EOLs are
ignored, so no conflict shown).

If you don't save the file now, the EOL conflict is kept. Just marking
the file as resolved won't change that.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-10-25 19:47:24 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.