On Sat, 18 Nov 2006 11:37:14 -0800 A Large Angry SCM <gitzilla@xxxxxxxxx> wrote: > I disagree. If a command is install on a system, it's man > pages/documentation should also be installed. Well this isn't a huge issue. One point you made though that struck a chord is that many of the commands should probably not be in section 1. > I'm also not convinced that there are a "large number of commands [...] > that should only ever be accessed as plumbing". I am convinced, however, > that there are a number of relatively low level commands with poor user > interfaces that are useful on their own. Is there really a reason for a git user to access these from the command line rather than a script: commit-tree, diff-files, diff-index, diff-tree, for-each-ref, hash-object, http-fetch, http-push, index-pack, local-fetch, merge-base, merge-index, merge-octopus, merge-one-file, merge-ours, merge-recur, merge-recursive, merge-recursive-old, merge-resolve, merge-stupid, merge-tree, receive-pack, runstatus, ssh-fetch, ssh-pull, ssh-push, ssh-upload, symbolic-ref, unpack-file, unpack-objects, update-ref, upload-archive, upload-pack, upload-tar, write-tree Not a complete list, and maybe i overlooked something in there that is needed from the command line, but for the most part these could be installed somewhere other than the users path. Sean - 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