Maxime Louet <maxime@xxxxxxxxx> writes: > Is this expected behaviour? I find it somehow confusing that the diff > in the commit message isn't the actual commit diff. Since the designed purpose of pre-commit hook is to examine the contents to be committed and reject the attempt to commit if there is something wrong found, and Git does not expect it to munge the contents to be committed, if the hook does so, you would get an undefined behaviour. So anything is totally expected at that point. Thanks.
