Evil merges in git - where do they come from?
        Posted  
        
            by Benjol
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by Benjol
        
        
        
        Published on 2010-06-18T13:00:19Z
        Indexed on 
            2010/06/18
            13:03 UTC
        
        
        Read the original article
        Hit count: 257
        
I've read this question and the answers, but what isn't clear to me is WHO creates the "changes that do not appear in any parent".
Is it the git merge algorithm screwing up?
Or is it because the user has to manually adjust the conflicts to get the thing to build, introducing new code which wasn't in either parent?
© Stack Overflow or respective owner