sorry, but I don't see the problem at all. Even though I only use git
since February 2008 (and I'm no kernel hacker at all...), I read through
the release notes regulary. 'git-foo' has been deprecated since version
1.4(!) and is finally disabled now, one and a half years later. Apart from
the too-many-executables argument, this is also the only way to move the
functions finally into one big executable which seems a Good Thing to me.
And its reasonable after all, just imagine you
had "ls-1", "ls-a", "ls-t"...
At some places, I was bitten by change also. The solution was simple: I
just stepped through the scripts, replaced "git-" with "git " (can be done
with a "sed"-oneliner), and the problem was solved once and for all. Are
kernel hackers so overworked that they just don't have time for this?
Posted Sep 4, 2008 8:55 UTC (Thu) by nix (subscriber, #2304)
[Link]
The moving-into-one-executable stuff has been happening for ages and is
not disrupted by having lots of names. All that happens is those names
become symlinks to /usr/bin/git, which is sensitive to argv[0].
(Besides, there are *still* lots of names: they're just in a different
place now, out of the default $PATH.)