Zitat von Junio C Hamano <gitster@xxxxxxxxx>: > However, I have to wonder if it is the right thing to do, like your patch > does, for "git --exec-path" to return "../libexec/git-core/" in a relative > form, without saying what it is relative to. Shouldn't we be showing the > full path after resolving that relative path to git executable? Does it? "git --exec-path" calls git_exec_path(), and that now returns system_path(GIT_EXEC_PATH), and that is an absolute path, although it's not normalized. Oh, I see: You tested it on Linux, right? This patch series does not work correctly on Linux (Unix? bash?), as Dscho has pointed out, since argv[0] does not have a directory part if "git" is in $PATH. In this case, system_path() just returns its argument, which is the relative path. :-/ -- Hannes -- 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
