On Wed, Apr 22, 2015 at 2:14 PM, Jeff King <peff@xxxxxxxx> wrote: > Subject: stop putting argv[0] dirname at front of PATH > > When the "git" wrapper is invoked, we prepend the baked-in > exec-path to our PATH, so that any sub-processes we exec > will all find the git-foo commands that match the wrapper > version. > [...] > Given that the main motivation for git pulling the argv[0] s/pulling/putting/ > dirname into the PATH has been broken for years, that the > remaining cases are obscure and unlikely (and easily fixed > by the user just setting up their $PATH sanely), and that > the behavior is hurting real, reasonably common use cases, > it's not worth continuing to do so. > > Signed-off-by: Jeff King <peff@xxxxxxxx> > --- > diff --git a/exec_cmd.c b/exec_cmd.c > index 8ab37b5..e85f0fd 100644 > --- a/exec_cmd.c > +++ b/exec_cmd.c > @@ -96,7 +96,6 @@ void setup_path(void) > struct strbuf new_path = STRBUF_INIT; > > add_path(&new_path, git_exec_path()); > - add_path(&new_path, argv0_path); > > if (old_path) > strbuf_addstr(&new_path, old_path); > -- > 2.4.0.rc2.498.g02440db -- 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