{"thread":{"id":"12070","subject":"setup_path()","startedAt":"2008-02-13T12:49:15Z","lastAt":"2008-02-14T01:54:05Z","messageCount":3,"participants":["David Miller","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"68639","messageId":"20080213.044915.123319879.davem@davemloft.net","threadId":"12070","inReplyTo":null,"subject":"setup_path()","fromName":"David Miller","fromEmail":"davem@davemloft.net","sentAt":"2008-02-13T12:49:15Z","receivedAt":"2008-02-13T12:49:15Z","isPatch":false,"sender":{"key":"davem@davemloft.net","avatar":null},"body":"\nShouldn't stand-alone programs other than git.c itself also call\nsetup_path()?\n\nI have a problem where if I only install git into my own home\ndirectory ~/bin, I can't send pull requests over SSH to that machine\nsuccessfully because the execvp() of \"pack-objects\" by git-upload-pack\nfails due to the PATH not containing \"git --exec-dir\"\n\nIf I add a dummy setup_path(NULL) call to upload-pack.c, it works\nfine.\n"},{"id":"68674","messageId":"7v3arwpqxj.fsf@gitster.siamese.dyndns.org","threadId":"12070","inReplyTo":"20080213.044915.123319879.davem@davemloft.net","subject":"Re: setup_path()","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-02-13T20:00:40Z","receivedAt":"2008-02-13T20:00:40Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"David Miller <davem@davemloft.net> writes:\n\n> Shouldn't stand-alone programs other than git.c itself also call\n> setup_path()?\n>\n> I have a problem where if I only install git into my own home\n> directory ~/bin, I can't send pull requests over SSH to that machine\n> successfully because the execvp() of \"pack-objects\" by git-upload-pack\n> fails due to the PATH not containing \"git --exec-dir\"\n>\n> If I add a dummy setup_path(NULL) call to upload-pack.c, it works\n> fine.\n\nYeah, Johannes Sixt had a patch to do exactly that earlier\n\n\tMessage-ID: <47B182C1.60006@viscovery.net>\n\thttp://news.gmane.org/gmane.comp.version-control.git/73651\n\nand I think it is a good idea to apply it.\n"},{"id":"68697","messageId":"20080213.175405.10792562.davem@davemloft.net","threadId":"12070","inReplyTo":"7v3arwpqxj.fsf@gitster.siamese.dyndns.org","subject":"Re: setup_path()","fromName":"David Miller","fromEmail":"davem@davemloft.net","sentAt":"2008-02-14T01:54:05Z","receivedAt":"2008-02-14T01:54:05Z","isPatch":false,"sender":{"key":"davem@davemloft.net","avatar":null},"body":"From: Junio C Hamano <gitster@pobox.com>\nDate: Wed, 13 Feb 2008 12:00:40 -0800\n\n> Yeah, Johannes Sixt had a patch to do exactly that earlier\n> \n> \tMessage-ID: <47B182C1.60006@viscovery.net>\n> \thttp://news.gmane.org/gmane.comp.version-control.git/73651\n> \n> and I think it is a good idea to apply it.\n\nMe too.\n\nIn fact people can easily end up unintentionally using different\nversions of GIT.  For example in my case I had the distribution's GIT\ninstalled in /usr/bin/git et al., then I installed the current\nupstream version of GIT in my home directory.\n\nA different version of GIT gets used when you run things locally\nvs. doing things remotely over SSH.  And I didn't notice this until I\nuninstalled the git-core package on my system.\n"}]}