Jeff King <p...@peff.net> writes: >> How about "and make sure any Git configuration files", since there >> might not be any Git configuration files. > > Yeah, that is better. Thanks.
OK, then... -- >8 -- Subject: [PATCH] doc: clarify that "git daemon --user=<user>" option does not export HOME=~user Signed-off-by: Jeff King <p...@peff.net> Helped-by: W. Trevor King <wk...@tremily.us> Signed-off-by: Junio C Hamano <gits...@pobox.com> --- Documentation/git-daemon.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt index 7e5098a..2ac07ba 100644 --- a/Documentation/git-daemon.txt +++ b/Documentation/git-daemon.txt @@ -147,6 +147,13 @@ OPTIONS Giving these options is an error when used with `--inetd`; use the facility of inet daemon to achieve the same before spawning 'git daemon' if needed. ++ +Like many programs that switch user id, the daemon does not reset +environment variables such as `$HOME` when it runs git programs, +e.g. `upload-pack` and `receive-pack`. When using this option, you +may also want to set and export `HOME` to point at the home +directory of `<user>` before starting the daemon, and make sure any +Git configuration files in that directory are readable by `<user>`. --enable=<service>:: --disable=<service>:: -- 1.8.2.1-472-g6c5785c -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
