{"thread":{"id":"10445","subject":"intended use of \"git --exec-path\"?","startedAt":"2007-10-24T04:32:24Z","lastAt":"2007-10-24T08:08:24Z","messageCount":5,"participants":["Scott Parish","Shawn O. Pearce","David Symonds","Andreas Ericsson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"57054","messageId":"20071024043224.GR16291@srparish.net","threadId":"10445","inReplyTo":null,"subject":"intended use of \"git --exec-path\"?","fromName":"Scott Parish","fromEmail":"srp@srparish.net","sentAt":"2007-10-24T04:32:24Z","receivedAt":"2007-10-24T04:32:24Z","isPatch":false,"sender":{"key":"srp@srparish.net","avatar":"https://gravatar.com/avatar/870e5b6fc4f710cf4db5684bd9af7f2cee5734b3dab3209b13e00cf64f6c9f0e?d=mp&s=160"},"body":"\"git --exec-path\" presently prints out the highest priority path\nto find executable in. That's a what; i'm curious why and when it\nshould be used. Basically i'm wondering if its still useful, and\nwhat, if anything, it should be printing.\n\nThanks\nsRp\n\n-- \nScott Parish\nhttp://srparish.net/\n"},{"id":"57055","messageId":"20071024043819.GI14735@spearce.org","threadId":"10445","inReplyTo":"20071024043224.GR16291@srparish.net","subject":"Re: intended use of \"git --exec-path\"?","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-10-24T04:38:19Z","receivedAt":"2007-10-24T04:38:19Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Scott Parish wrote:\n> \"git --exec-path\" presently prints out the highest priority path\n> to find executable in. That's a what; i'm curious why and when it\n> should be used. Basically i'm wondering if its still useful, and\n> what, if anything, it should be printing.\n\ngit-gui uses it. git-gui runs git-* by prefixing it with the\nexec path. It also scans the first line of the file if we are on\nWindows and the \"executable\" doesn't end in \".exe\" so it can figure\nout what process to run it through.\n\nSo it really can't go away.\n\n-- \nShawn.\n"},{"id":"57060","messageId":"20071024054749.GT16291@srparish.net","threadId":"10445","inReplyTo":"20071024043819.GI14735@spearce.org","subject":"Re: intended use of \"git --exec-path\"?","fromName":"Scott Parish","fromEmail":"srp@srparish.net","sentAt":"2007-10-24T05:47:49Z","receivedAt":"2007-10-24T05:47:49Z","isPatch":false,"sender":{"key":"srp@srparish.net","avatar":"https://gravatar.com/avatar/870e5b6fc4f710cf4db5684bd9af7f2cee5734b3dab3209b13e00cf64f6c9f0e?d=mp&s=160"},"body":"On Wed, Oct 24, 2007 at 12:38:19AM -0400, Shawn O. Pearce wrote:\n\n> Scott Parish wrote:\n> > \"git --exec-path\" presently prints out the highest priority path\n> > to find executable in. That's a what; i'm curious why and when it\n> > should be used. Basically i'm wondering if its still useful, and\n> > what, if anything, it should be printing.\n> \n> git-gui uses it. git-gui runs git-* by prefixing it with the\n> exec path. It also scans the first line of the file if we are on\n> Windows and the \"executable\" doesn't end in \".exe\" so it can figure\n> out what process to run it through.\n> \n> So it really can't go away.\n\nSo it sounds like it might be more helpful for git to return its\nPATH, so other programs can set their PATH or search for executables\naccordingly.\n\nsRp\n\n-- \nScott Parish\nhttp://srparish.net/\n"},{"id":"57061","messageId":"ee77f5c20710232254j32afa044t841b4a4f6fcdfd7d@mail.gmail.com","threadId":"10445","inReplyTo":"20071024054749.GT16291@srparish.net","subject":"Re: intended use of \"git --exec-path\"?","fromName":"David Symonds","fromEmail":"dsymonds@gmail.com","sentAt":"2007-10-24T05:54:52Z","receivedAt":"2007-10-24T05:54:52Z","isPatch":false,"sender":{"key":"dsymonds@gmail.com","avatar":"https://gravatar.com/avatar/b22f5051cbfc11836e36cf7a690e6cde4e225d835e13295ff98d15c7a9ee3c0f?d=mp&s=160"},"body":"On 10/24/07, Scott Parish wrote:\n> On Wed, Oct 24, 2007 at 12:38:19AM -0400, Shawn O. Pearce wrote:\n>\n> > Scott Parish wrote:\n> > > \"git --exec-path\" presently prints out the highest priority path\n> > > to find executable in. That's a what; i'm curious why and when it\n> > > should be used. Basically i'm wondering if its still useful, and\n> > > what, if anything, it should be printing.\n> >\n> > git-gui uses it. git-gui runs git-* by prefixing it with the\n> > exec path. It also scans the first line of the file if we are on\n> > Windows and the \"executable\" doesn't end in \".exe\" so it can figure\n> > out what process to run it through.\n> >\n> > So it really can't go away.\n>\n> So it sounds like it might be more helpful for git to return its\n> PATH, so other programs can set their PATH or search for executables\n> accordingly.\n\nYou don't necessarily want to be monkeying around with $PATH if you're\ntrying to use a particular git installation (say, a build of next)\ninstead of your \"proper\" install, which is in your $PATH; if you call\n/some/random/path/git-whatever, it should use the git tools in\n/some/random/path/, not in $PATH.\n\n\nDave.\n"},{"id":"57065","messageId":"471EFD78.6030206@op5.se","threadId":"10445","inReplyTo":"20071024043224.GR16291@srparish.net","subject":"Re: intended use of \"git --exec-path\"?","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-10-24T08:08:24Z","receivedAt":"2007-10-24T08:08:24Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Scott Parish wrote:\n> \"git --exec-path\" presently prints out the highest priority path\n> to find executable in. That's a what; i'm curious why and when it\n> should be used. Basically i'm wondering if its still useful, and\n> what, if anything, it should be printing.\n> \n\ngit supports having all its \"helpers\" in a separate path. Since\nthere were performance concerns with having scripts call the git\nwrapper for every invocation of every git program, the --exec-path\noption was added when the wrapper was rewritten in C.\n\nUnless it's a very tight loop that runs non-builtin programs,\nthere's really no reason for scripts to use the git-whatever form\nof commands, but the ability to do so should probably be retained\nmore or less forever. See 8e49d50388211a0f3e7286f6ee600bf7736f4814\nfor details.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"}]}