Re: [PATCH] Move all dashed form git commands to libexecdir
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Nov 29, 2007, 20:05 UTC
- Message-ID
- <fcaeb9bf0711291205h125dadbbp8e8ae392e9b5b751@mail.gmail.com>
- In-Reply-To
- <20071129150849.GA32296@coredump.intra.peff.net>
On Nov 29, 2007 10:08 PM, Jeff King <peff@peff.net> wrote:
Show 21 quoted lines
> On Wed, Nov 28, 2007 at 03:14:56PM -0800, Junio C Hamano wrote: > > > - Post v1.5.5, start cooking the change that does not install hardlinks > > for built-in commands, aiming for inclusion in v1.6.0, by the end of > > 2008. > > I am against this, unless it is configurable. I think the goal of > reducing user-visible commands is fine, and moving things to > $(libexecdir) is a good way of doing that. > > However, I personally still think the 'git-foo' forms are valuable > (because fingers have already been trained, and because > non-bash-programmable completions understand them). And I don't mind > putting $(libexecdir)/git-core in my PATH to retain this behavior; it's > a one-time configuration tweak, and it helps new users with the > overwhelming command set. > > But I don't see a point to removing the links entirely. The annoyance > factor for people who want git-* is much higher, and I don't see that it > actually buys us any help for new users (who will no longer care after > everything is hidden in $(libexecdir) anyway).
Maybe only not install hardlinks on systems that do not support it like Windows? git.exe duplication takes a lot of space.
-- Duy