{"thread":{"id":"14680","subject":"how about removing --exec-path?","startedAt":"2008-07-25T09:40:15Z","lastAt":"2008-07-26T06:48:31Z","messageCount":3,"participants":["Alex Riesen","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"84924","messageId":"20080725094015.GA22077@blimp.local","threadId":"14680","inReplyTo":null,"subject":"how about removing --exec-path?","fromName":"Alex Riesen","fromEmail":"fork0@users.sourceforge.net","sentAt":"2008-07-25T09:40:15Z","receivedAt":"2008-07-25T09:40:15Z","isPatch":false,"sender":{"key":"fork0@users.sourceforge.net","avatar":null},"body":"The thing has at least this problem: is not passed to upload-pack when\nrunning fetch. So upload-pack, everything past it gets called either\nfrom GIT_EXEC_PATH (which usually is not set) or from builtin exec\npath (and that's annoying when debugging for instance index-pack).\n\nThe feature has a stable alternative ($GIT_EXEC_PATH) anyway.\n\nOr maybe just replace the whole argv_exec_path handling with a plain\nsetenv(\"GIT_EXEC_PATH\", exec_path, 1)?\n"},{"id":"84990","messageId":"alpine.DEB.1.00.0807260448210.26810@eeepc-johanness","threadId":"14680","inReplyTo":"20080725094015.GA22077@blimp.local","subject":"Re: how about removing --exec-path?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-07-26T02:49:06Z","receivedAt":"2008-07-26T02:49:06Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 25 Jul 2008, Alex Riesen wrote:\n\n> The thing has at least this problem: is not passed to upload-pack when\n> running fetch.\n\nIt should be added to PATH, and so it is passed to upload-pack, amongst \nothers, in a sense.\n\nCiao,\nDscho\n"},{"id":"85020","messageId":"20080726064831.GA3698@blimp.local","threadId":"14680","inReplyTo":"alpine.DEB.1.00.0807260448210.26810@eeepc-johanness","subject":"Re: how about removing --exec-path?","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2008-07-26T06:48:31Z","receivedAt":"2008-07-26T06:48:31Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Johannes Schindelin, Sat, Jul 26, 2008 04:49:06 +0200:\n> On Fri, 25 Jul 2008, Alex Riesen wrote:\n> \n> > The thing has at least this problem: is not passed to upload-pack when\n> > running fetch.\n> \n> It should be added to PATH, and so it is passed to upload-pack, amongst \n> others, in a sense.\n> \n\nYes, but next time upload-pack runs a program, it adds builtin exec\npath to PATH (because --exec-path not given to transport's uploadpack\ncommand). So it looks like this:\n\n    $GIT_EXEC_PATH:/usr/local/libexec/git-core:/orig/exec-path:\\\n    $GIT_EXEC_PATH:/usr/local/libexec/git-core:$ORIG_USER_PATH\n\nwhich kind of useless for debugging. So using GIT_EXEC_PATH is the\nonly way (and why did we need more? Working around something?)\n"}]}