On Fri, Mar 4, 2011 at 11:18 AM, John Found <[email protected]> wrote:
> Several times when making merge with fossil, I ended up with really strange > conflicts like this: > > <<<<<<< BEGIN MERGE CONFLICT: original content first <<<<<<< > include '%TargetOS%/mouse.asm'======= original content above; conflict > below ============= > include '%TargetOS%/mouse.asm'>>>>>>> END MERGE CONFLICT: conflict last > >>>>>>>>>>>>>>>>>> > Did it really come out looking like that, or did the line wrapping occur when you pasted the output in to your email program? Differences might be whitespace. Extra whitespace at the end of the line, or tabs instead of spaces someplace. Or, could it be that your files does not end with a \n and that fact is confusing Fossil somehow? If so, I'll look into it. But a quick fix for you is to make sure your source code files end with \n - something you should probably be doing anyhow. > > In one merge, there was 4..5 similar "conflicts" and none of "real" > In my opinion, both lines are totally equal. > Is it a bug or I am missing something? > > Regards > > http://fresh.flatassembler.net > Assembly language visual programming. > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
