Scott Parish <sRp@srparish.net> writes:"git" binary will be found as /usr/bin/git while git-foo will be found as /usr/libexec/git/git-foo in such an installation that takes advantage of $(gitexecdir). And /usr/libexec/git/git will not exist. Using existence of /usr/bin/git (I am referring to your 'first directory on $PATH that contains the "git" binary' above) as the cue for the location of "main commands" is wrong. It's up to you. Obviously, if you are replacing 2 patches out of 100-patch series, you would not want to resend the whole thing, though ;-) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian | [RFC/PATCH] RE: git calls SSH_ASKPASS even if DISPLAY is not set |
| Junio C Hamano | Re: Rss produced by git is not valid xml? |
