(minor) document what to do when you have *two* gits
...and the wrong one ends up runing
This commit is contained in:
parent
8d55bd722c
commit
461a581322
|
@ -485,6 +485,17 @@ attempting to run git stuff.
|
||||||
|
|
||||||
Very easy, very simple, and completely transparent to the users :-)
|
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
|
||||||
|
|
||||||
"personal" branches are great for corporate environments, where
|
"personal" branches are great for corporate environments, where
|
||||||
|
|
Loading…
Reference in a new issue