So, at some point before this, you merged two branches. I'm guessing you confused git-checkout with git-pull. There were apparently merge conflicts, and git added markers around the conflicts so you could find them.
Believe it or not, that's a good thing. You don't want these files to compile without having a human to look over them first. The code might compile, but do the two conflicting things in the wrong order, they might be variations of the same thing, and do it twice when it should be done once, or who knows what else.
So, anyway, you apparently tried to do something else that required a merge - probably using git-pull again - and it wouldn't let you because the previous merge wasn't fixed yet.
So, you decide you've had enough with source control, and try to be productive and get some code written, only to find it doesn't compile because of the merge conflicts you accidently introduced earlier.
So; you'll probably want to revert this to back before you accidently merged your two branches, but if not, the way to fix merge conflicts is to use git-status to list the files that need resolution, search for ==== to find and manually fix the conflicts, use git-add on the fixed files, and finally git-commit to tell it everythings better now and to finish the merge.