Re: [PATCH] Move all dashed form git commands to libexecdir
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Nov 30, 2007, 12:19 UTC
- Message-ID
- <fcaeb9bf0711300419i9cf70eo9f96e3a5e3f44585@mail.gmail.com>
- In-Reply-To
- <DB613F3E-85CC-4AF0-928C-4F4E4C8E9FB8@orakel.ntnu.no>
On Nov 30, 2007 6:28 PM, Eyvind Bernhardsen <eyvind-git-list@orakel.ntnu.no> wrote:
Show 23 quoted lines
> On 29. nov. 2007, at 23.36, Junio C Hamano wrote: > > [...] > > > If people are really serious about reducing the number of commands in > > the path, I would expect fixes and bugreports saying "I am setting > > gitexecdir different from bindir in _my_ installation when I build > > git, > > and here are the things that does not work if I do so". Within the > > span > > of more than 20 months (77cb17e9 introduced gitexecdir in Jan 2006), I > > do not think there was a single such report or patch, other than the > > message from Nguyen that started this thread. > > I'm setting gitexecdir different from bindir in my installation, and > here are the things that don't work: > > - When pushing to my system over ssh, git-receive-pack and git-upload- > pack are expected to be in $PATH. I resolved the problem by putting > symlinks in /usr/local/bin. > > I haven't seen any other problems, but then again, I only use git > plumbing commands and my own scripts.
You remind me my experience of making every external C-based command builtin. There is another case: git-merge. It calls something like git-merge-$strategy.
-- Duy