c819aa0606
...to avoid misguided clang-format'ing of previously excluded files, as discussed in the comment at <https://gerrit.libreoffice.org/c/core/+/142387/4#message-ce27921261661fe7488ef0564657dbb5b42fb5fa> "sc: factor out common code in make files". (Though this still doesn't warn about cases where some excluded file got renamed and the excludelist wasn't updated and the user already erroneously clang-format'ed the renamed file before this commit attempt. Also, I don't know how best to integrate this with libreoffice.autostyle, so just ignore libreoffice.autostyle for now when any suspicious renames are detected.) Change-Id: I8d176ce536548b67f5b2af100f579f362764b06b Reviewed-on: https://gerrit.libreoffice.org/c/core/+/142394 Tested-by: Jenkins Reviewed-by: Stephan Bergmann <sbergman@redhat.com> |
||
|---|---|---|
| .. | ||
| commit-msg | ||
| post-merge | ||
| pre-commit | ||
| README | ||
Git hooks are executable scripts you can place in $GIT_DIR/hooks directory to trigger action at certain points. To install manually, run: cd .git/hooks && ln -s ../../.git-hooks/* ./ When you using GIT for Windows, you need Windows links Open a Dos-Box with admin rights then cd .git/hooks FOR /F " usebackq " %i IN (`dir /b ..\..\.git-hooks`) DO mklink %i ..\..\.git-hooks\%i There are two groups of these hooks: client side and server side. The client-side hooks: are for client operations such as committing and merging. The server-side hooks: are for Git server operations such as receiving pushed commits. See Also [ http://git-scm.com/book/en/Customizing-Git-Git-Hooks ]