9afc6b22e2
Always when you call build or logerrit, then the windows-links overwrite with linux-links, but when you using GIT for Windows you need the windows-links. This patch made a check it is using GIT for Windows, and check what for link it is, when wrong link, it output the .git-hooks/README Improve the check for links, when a link is set not need to set the link anymore In .git-hooks/README improve the FOR with delete of the wrong link look here for GIT for Windows: https://wiki.documentfoundation.org/Development/BuildingOnWindows/de#Cygwin_and_git Change-Id: I9f6ef9aca316058ef74cb2b2d107236f03a2e2ee Reviewed-on: https://gerrit.libreoffice.org/c/core/+/147458 Tested-by: Jenkins Reviewed-by: Thorsten Behrens <thorsten.behrens@allotropia.de> |
||
|---|---|---|
| .. | ||
| 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 del /as /f %i & 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 ]