On Mon, Nov 26, 2007 at 20:34:25 +0100, David Kastrup wrote: > Nicolas Pitre <nico@xxxxxxx> writes: > > On Mon, 26 Nov 2007, David Kastrup wrote: > >> Get rid of plumbing at the command line level. > > > > We can't get rid of plumbing. > > What about "at the command line level" did you not understand? Which part of we neither can nor want did you not understant? The availability of plumbing is really big part of a reason why git is so good and has so many scripts and tool built on top of it. Bzr and hg boast with their ability to add plugins, but git ability to use plumbing simply beats that hands down, because the plugins are python-only and writing them requires understanding the internal API, while git plumbing can be used from any language and can usually be understood by running it interactively a few times. That's why we don't want (and really can't because there is a huge amount of code in various languages using it) to get rid of plumbing at the command level. What we may do is hide it from the casual user. To do that, we'd want to get rid of the git-* commands and links in bin (remove the builtins altogether and move the non-builtin to libexec -- that seems to be the plan for 1.6 or 1.7 already) and than hiding the plumbing from --help and completion hides it from the user. -- Jan 'Bulb' Hudec <bulb@xxxxxx> - 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
