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

Re: de-alphabetizing the documentation

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Jul 6, 2018, 21:32 UTC
Message-ID
<20180706213239.GA867@flurp.local>
In-Reply-To
<20180706211600.GB6195@aiede.svl.corp.google.com>
On Fri, Jul 06, 2018 at 02:16:00PM -0700, Jonathan Nieder wrote:
Show 8 quoted lines
> Frederick Eaton wrote:
> > I wonder if someone familiar with Git could list the commands in an
> > order which makes more sense for learning, for example in the order in
> > which they were invented by Git developers,
> 
> Alas, there are plenty of "Main porcelain commands", and I think that
> is where your question comes from.  It would be nicer to list just five
> to start, say.

"git help" makes some attempt at narrowing the list of porcelain commands likely to be used on an everyday basis (and it categorizes the list by general activity). Of the 21 commands listed, I use 14-16 in pretty much every development session, so "git help" might be a good starting place for someone trying to figure out which commands to study, or for someone wishing to help focus the documentation a bit more for beginners.

--- >8 --- $ git help usage: git ...

These are common Git commands used in various situations:
start a working area (see also: git help tutorial)
   clone      Clone a repository into a new directory
   init       Create an empty Git repository or reinitialize an existing one
work on the current change (see also: git help everyday)
   add        Add file contents to the index
   mv         Move or rename a file, a directory, or a symlink
   reset      Reset current HEAD to the specified state
   rm         Remove files from the working tree and from the index
examine the history and state (see also: git help revisions)
   bisect     Use binary search to find the commit that introduced a bug
   grep       Print lines matching a pattern
   log        Show commit logs
   show       Show various types of objects
   status     Show the working tree status
grow, mark and tweak your common history
   branch     List, create, or delete branches
   checkout   Switch branches or restore working tree files
   commit     Record changes to the repository
   diff       Show changes between commits, commit and working tree, etc
   merge      Join two or more development histories together
   rebase     Reapply commits on top of another base tip
   tag        Create, list, delete or verify a tag object signed with GPG
collaborate (see also: git help workflows)
   fetch      Download objects and refs from another repository
   pull       Fetch from and integrate with another repository or a local branch
   push       Update remote refs along with associated objects

'git help -a' and 'git help -g' list available subcommands and some concept guides. See 'git help <command>' or 'git help <concept>' to read about a specific subcommand or concept. --- >8 ---

Previous: Jonathan NiederNext: frederik@ofb.net
Message 4 of 17 in “de-alphabetizing the documentation”
  1. frederik@ofb.netJul 6, 2018
  2. Jonathan NiederJul 6, 2018
  3. Jonathan NiederJul 6, 2018
  4. Eric SunshineJul 6, 2018
  5. frederik@ofb.netJul 6, 2018
  6. Jonathan NiederJul 6, 2018
  7. frederik@ofb.netJul 8, 2018
  8. frederik@ofb.netJul 24, 2018
  9. Jonathan NiederJul 24, 2018
  10. frederik@ofb.netAug 11, 2018
  11. Junio C HamanoAug 13, 2018
  12. 0/1 de-alphabetize command listFrederick Eaton, Feb 19, 2019
  13. frederik@ofb.netFeb 21, 2019
  14. frederik@ofb.netMar 11, 2019
  15. Jacob KellerMar 11, 2019
  16. Prioritize list of commands appearing in git(1), via command-list.txt. Don't invoke 'sort' in Documentation/cmd-list.perl.Frederick Eaton, Feb 19, 2019
  17. Theodore Y. Ts'oJul 7, 2018

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.