SynoCommunity/spksrc — comment on commit 6a1865fa4215d34f0186650f323f1cd7a8680b82
File:  line 0
By Diaoul:

From [StackOverflow](http://stackoverflow.com/questions/5443010/wrong-file-permission-when-using-git-pull-in-a-hook):

> Git does not store permissions, apart from the executable bit. So, on checkout, files are created with the default permissions, which depend on your umask.
>
> I guess, when you are calling the hook manually, you have a more liberal umask set. You can override the umask with the umask shell command. For your purposes, 0022 is probably fine.

But that's not related to your problem. I think this may be the normal behavior because you commited before pulling so you need a merge to catch up.
You need it to catch up changes since your last pull/fetch. This merge sums up what happened in the interval of time (the two commits from Nounours44).
Here another example: https://github.com/kennethreitz/requests/commit/d343fda7f099b8a76a440999e79e3c53229f44aa
If you do not want this to happen you can rebase.

An excellent article on this subject here (in french) http://dmathieu.com/fr/git/rebase-vs-merge