From 461a58132292e53089bd4b3a75e7bddcc1edcd75 Mon Sep 17 00:00:00 2001 From: Sitaram Chamarty Date: Wed, 14 Apr 2010 23:16:29 +0530 Subject: [PATCH] (minor) document what to do when you have *two* gits ...and the wrong one ends up runing --- doc/3-faq-tips-etc.mkd | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/3-faq-tips-etc.mkd b/doc/3-faq-tips-etc.mkd index 5939832..f0c7afa 100644 --- a/doc/3-faq-tips-etc.mkd +++ b/doc/3-faq-tips-etc.mkd @@ -485,6 +485,17 @@ attempting to run git stuff. Very easy, very simple, and completely transparent to the users :-) +**Note**: sometimes you have a system that already has an older "git" +installed in one of the system PATHs, but you've installed a newer git in some +non-standard location and want that picked up. Because of security reasons, +gitolite will not prepend `GIT_PATH` to the PATH variable, so the older git +comes first and it gets kinda frustrating! + +Here's a simple workaround. Ignore the `GIT_PATH` variable, and directly set +the full PATH in the rc file, like so: + + $ENV{PATH} = "/home/sitaram/bin:$ENV{PATH}"; + #### "personal" branches "personal" branches are great for corporate environments, where