git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Document git-runstatus

From
Sean <seanlkml@sympatico.ca>
Date
Nov 18, 2006, 20:04 UTC
Message-ID
<BAYC1-PASMTP103AEE0623ACD61079E916AEEF0@CEZ.ICE>
In-Reply-To
<455F60EA.2080009@gmail.com>

On Sat, 18 Nov 2006 11:37:14 -0800 A Large Angry SCM <gitzilla@gmail.com> 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.

Previous: Junio C HamanoNext: Petr Baudis
Message 9 of 12 in “Document git-runstatus”
  1. Document git-runstatusRene Scharfe, Nov 18, 2006
  2. SeanNov 18, 2006
  3. Petr BaudisNov 18, 2006
  4. Rene ScharfeNov 18, 2006
  5. SeanNov 18, 2006
  6. A Large Angry SCMNov 18, 2006
  7. SeanNov 18, 2006
  8. Junio C HamanoNov 18, 2006
  9. SeanNov 18, 2006
  10. Petr BaudisNov 19, 2006
  11. Joshua N PritikinNov 20, 2006
  12. Jakub NarebskiNov 20, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.