Now those are technical merges when comes when one does git merge to his local repo , when doing git pull , basiclly. Those my traces of doing git pull. I haven't being doing that, because usually I am the only contributor to this repo
![Sad :(](./images/smilies/icon_sad.png)
.
Yes, that's why I would encourage you to do a: 'git pull --rebase' next times in such cases to avoid seeing those merge commits in the log.
My question is not about the look of those merge commits but whether you could check to resulting repository files line endings and correct them if they're wrong. Could you do that for me?
![Smile :)](./images/smilies/icon_smile.png)
What needs to be merged is merged already. In git you can remove only branch tags , the commits would stay there , and after removing those branches the code there would become unreachable. Why should I do that ?
I didn't understand that one very well, but may I assume you mean the branches other than 'development' are plain obsolete?
In that case, let's get rid of them. Who cares about the code there being unreachable if it's useless?