Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes: > Maybe just say > > * Do not install all git subcommands as 'git-xyzzy' files in the user > path. This avoids unnecessary hardlinks (or copies on systems that do > not support links), and enforces the 'git xyzzy' syntax. > > Subcommands that aren't builtins now get installed in > /usr/libexec/git-core/ or somesuch. Thanks. > (I haven't looked at the series, but I _assume_ it also avoids installing > the builtin subcommands entirely when not necessary, ie "git-cat-file" > really _is_ gone, but it's not because the "cat-file" command itself is > gone). It is actually a fairly long road ahead. In 1.6.0, most of them will be moved to /usr/libexec/git-core/, so that really old scripts end users may have can be more easily kept working by simply saying: PATH=$(git --exec-path):$PATH early, without doing "s/git-/git /g". Current git clients run git-upload-pack and friends in "git-xyzzy" form when accessing remote repositories directly over ssh, so in 1.6.0 we will have to leave these server side programs in $(bindir) as well. git-shell and gitosis is being updated to accept "git upload-pack" form as well, and after older versions of these programs die out, we can update the clients to ask for remote side programs without dash. None of the server side programs is built-in, so we could start the hardlink removal independent from this transition (iow, "Only subcommands that aren't builtin will be installed in libexec, builtins are not on the disk anywhere" could happen now), but I'd prefer to keep changes in each steps small to minimize impacts to the end users' environments. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
