Re: do people use the 'git' command?

JS> Then:

JS>     git update-cache 

JS> would work as expected.

I'd rather teach the user to say git-update-cache once they learned how git works.

Let's stop and think. Compare lower level binaries and git-*-script commands, especially paying attention to the level of operation of what they do. Notice the difference?

The git-*-script commands are already more or less Porcelain themselves, and for that reason alone, they deserve to have CVS/SVN familiarity wrapper. They are designed to be usable even by people who are still not familiar with the GIT way of doing things, and the purpose of the "git" wrapper is to help these people try putting their toes in the water. Once they understand how these scripts work, they either care about Plumbing because they want to do something existing Porcelain layers do not offer (in which case they would write their own Porcelain extensions using Plumbing commands). Or with luck, they may not have to worry about Plumbing at all.

I grant you that what the current "git" wrapper offers is not Porcelain enough, and to perform anything meaningful you either need to use Porcelain or bare Plumbing commands yourself. But when that day comes, "git update-cache" is not something you would want to have anyway. You would rather want to have things like "git add" and "git remove", which are written in terms of git-update-cache.

See what I am saying?