systemd-stable/tools/add-git-hook.sh

#!/bin/sh
set -eu

cd "$MESON_SOURCE_ROOT"

if [ ! -f .git/hooks/pre-commit.sample -o -f .git/hooks/pre-commit ]; then
    exit 2 # not needed
fi

cp -p .git/hooks/pre-commit.sample .git/hooks/pre-commit
chmod +x .git/hooks/pre-commit
echo 'Activated pre-commit hook'
separate flags from shebang 2017-12-24 06:53:20 +00:00			`#!/bin/sh`
			`set -eu`
meson: install the git hook (#6425) This was done autogen.sh previously and was dropped in 72cdb3e783174dcf9223a49f03e3b0e2ca95ddb8. Let's add it back. The meson configuration step is the only reasonable place. Note that this only works for the most standard git dirs, e.g. the hook will not be installed if git worktree is used or if $GIT_DIR is specified, etc. I think that's OK because most of the time meson will be run at least once in the original cloned dir. 2017-07-24 04:41:45 -04:00
			`cd "$MESON_SOURCE_ROOT"`

			`if [ ! -f .git/hooks/pre-commit.sample -o -f .git/hooks/pre-commit ]; then`
scripts: use 4 space indentation We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes. 2019-04-04 14:10:42 +02:00			`exit 2 # not needed`
meson: install the git hook (#6425) This was done autogen.sh previously and was dropped in 72cdb3e783174dcf9223a49f03e3b0e2ca95ddb8. Let's add it back. The meson configuration step is the only reasonable place. Note that this only works for the most standard git dirs, e.g. the hook will not be installed if git worktree is used or if $GIT_DIR is specified, etc. I think that's OK because most of the time meson will be run at least once in the original cloned dir. 2017-07-24 04:41:45 -04:00			`fi`

			`cp -p .git/hooks/pre-commit.sample .git/hooks/pre-commit`
			`chmod +x .git/hooks/pre-commit`
			`echo 'Activated pre-commit hook'`