On Fri, Dec 07, 2007 at 02:39:24AM -0800, Junio C Hamano wrote:
Usually, if a user has his own version of git and regularly uses it by having the non-system executable directory (e.g. $HOME/bin/git) early in his $PATH, its corresponding documentation would also be in a non-system documentation directory (e.g. $HOME/man) early in his $MANPATH, and this change is a no-op. The only case this change matters is where the user installs his own git outside of his $PATH and $MANPATH, and explicitly runs his git executable (e.g. "$HOME/junk/git-1.5.4/bin/git diff"). When you clarify it this way, the change does not look as useful anymore, does it? How typical would that use be, to run your git executable by always naming it by path without relying on $PATH environment variable?
Or, git gets installed out of path in its own tree, and then the 'git' executable itself is symlinked somewhere into the path. I know this happens, because this is what IT ended up doing. It's also fairly easy to add a new executable path, and forget to add a new manpath directory. Dave - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
