2 These config entries specify Git-tracked directories that are
3 considered safe even if they are owned by someone other than the
4 current user. By default, Git will refuse to even parse a Git
5 config of a repository owned by someone else, let alone run its
6 hooks, and this config setting allows users to specify exceptions,
7 e.g. for intentionally shared repositories (see the `--shared`
8 option in linkgit:git-init[1]).
10 This is a multi-valued setting, i.e. you can add more than one directory
11 via `git config --add`. To reset the list of safe directories (e.g. to
12 override any such directories specified in the system config), add a
13 `safe.directory` entry with an empty value.
15 This config setting is only respected when specified in a system or global
16 config, not when it is specified in a repository config or via the command
17 line option `-c safe.directory=<path>`.
19 The value of this setting is interpolated, i.e. `~/<path>` expands to a
20 path relative to the home directory and `%(prefix)/<path>` expands to a
21 path relative to Git's (runtime) prefix.