{"thread":{"id":"48834","subject":"de-alphabetizing the documentation","startedAt":"2018-07-06T20:37:44Z","lastAt":"2019-03-11T14:38:20Z","messageCount":17,"participants":["frederik@ofb.net","Jonathan Nieder","Eric Sunshine","Theodore Y. Ts'o","Junio C Hamano","Frederick Eaton","Jacob Keller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"351812","messageId":"20180706200423.GC6343@ofb.net","threadId":"48834","inReplyTo":null,"subject":"de-alphabetizing the documentation","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2018-07-06T20:04:23Z","receivedAt":"2018-07-06T20:37:44Z","isPatch":false,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Dear Git Developers,\n\nI am trying to learn how to use Git but I've been put off by not\nknowing where to start. I would like to start with the 'git' man page,\nbut it lists the Git subcommands in alphabetical order, rather than in\nan order which would be useful for learners. For example, I'm not sure\nhow often 'git bisect' is used, but it is strange to see it listed\nbefore 'git init' and 'git clone'.\n\nI know that 'gittutorial' exists, and I've indeed worked through it\nand some other Git tutorials. However, these are more like lists of\nexamples that should come at the end of a typical manual page. I don't\nthink they are intended as canonical references for the program\nfunctionality. At some point I would like to use the main 'git' manual\npage as my primary source of documentation. This would be easier if it\nwere designed to be read straight through.\n\nI wonder if someone familiar with Git could list the commands in an\norder which makes more sense for learning, for example in the order in\nwhich they were invented by Git developers, or in the reverse order of\nfrequency of use by a typical Git user. This could easily be derived\nfrom the shell history of someone who is reading this.\n\n    (cat ~/.bash_history; cut -d \";\" -f 2 ~/.zsh_history) | grep '^git ' | cut -d ' ' -f 2 | sort | uniq -c | sort -nr\n\nI would like to have this list for personal use, but once it is\ncreated, perhaps someone could also add it to the main Git man page.\nThe list could be added at the top of the \"GIT COMMANDS\" section.\nAlternatively, and I think preferably, the entries in that section\ncould be rearranged into this order.\n\nFinally, perhaps the same listing and/or reordering could be done for\nother important manual pages, like 'gitglossary'. Presumably\n'gitglossary' should be sorted topologically, so that each term is\ndefined prior to any terms depending on it.\n\nI'm not sure why alphabetical order was decided upon, but it seems\nless than useful in the information age, when people can easily search\nfor text electronically. Maybe at some point someone decided to \"clean\nup\" the presentation by alphabetizing the manual page. As a user who\nis more concerned with substance, it is annoying to encounter such an\nemphasis on the superficial, which seems unworthy of such an important\npiece of software.\n\nThank you,\n\nFrederick Eaton\n"},{"id":"351814","messageId":"20180706211600.GB6195@aiede.svl.corp.google.com","threadId":"48834","inReplyTo":"20180706200423.GC6343@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-07-06T21:16:00Z","receivedAt":"2018-07-06T21:16:06Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Frederick,\n\nFrederick Eaton wrote:\n\n> I am trying to learn how to use Git but I've been put off by not\n> knowing where to start. I would like to start with the 'git' man page,\n> but it lists the Git subcommands in alphabetical order, rather than in\n> an order which would be useful for learners. For example, I'm not sure\n> how often 'git bisect' is used, but it is strange to see it listed\n> before 'git init' and 'git clone'.\n[...]\n> I wonder if someone familiar with Git could list the commands in an\n> order which makes more sense for learning, for example in the order in\n> which they were invented by Git developers,\n\nThat doesn't seem like a useful order pedagogically, but\n\n>                                             or in the reverse order of\n> frequency of use by a typical Git user.\n\nThat does.\n\nCurrently the commands are already broken into a few categories:\n\n  High-level commands\n    Main porcelain commands\n    Ancillary commands\n    Interacting with others\n  Low-level commands\n    Manipulation commands\n    Interrogation commands\n    Synching repositories\n    Internal helper commands\n\nWhile it's alphabetical within each section, overall it is not\nalphabetical at all!\n\nAlas, there are plenty of \"Main porcelain commands\", and I think that\nis where your question comes from.  It would be nicer to list just five\nto start, say.\n\nSome of the most thoughtful documentation that comes with Git is at\nhttps://www.kernel.org/pub/software/scm/git/docs/user-manual.html.\nIt might be useful for inspiration.\n\nIdeas?  If you start with a proposal, we're happy to help refine it.\nPeople in the #git channel on irc.freenode.net (wechat.freenode.net)\nmight also be useful for inspiration in coming up with a proposal.\n\nEach of us have our weaknesses for this kind of work: you're telling\nme you're too new to have a sense of which commands are the first a\nperson would need to learn (and I have no reason to doubt you), while\nmany on this list would have the opposite problem of taking too much\nfor granted and not being able to put themselves in the mind of a\nnewcomer.  So we'll have to help each other.\n\ntl/dr: if you come up with a proposed \"first commands to learn\"\ncategory with some proposed commands to go in it, we'll be happy to\nhelp you with the next steps.\n\n[...]\n> Finally, perhaps the same listing and/or reordering could be done for\n> other important manual pages, like 'gitglossary'. Presumably\n> 'gitglossary' should be sorted topologically, so that each term is\n> defined prior to any terms depending on it.\n\nYour help is welcome here as well.  Probably a similar kind of\ncategorization, with entries ordered either alphabetically or\naccording to some narrative in each section, would be the easiest to\nmaintain over time.\n\nThanks,\nJonathan\n"},{"id":"351815","messageId":"20180706211828.GC6195@aiede.svl.corp.google.com","threadId":"48834","inReplyTo":"20180706211600.GB6195@aiede.svl.corp.google.com","subject":"Re: de-alphabetizing the documentation","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-07-06T21:18:28Z","receivedAt":"2018-07-06T21:18:33Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Jonathan Nieder wrote:\n\n> Ideas?  If you start with a proposal, we're happy to help refine it.\n> People in the #git channel on irc.freenode.net (wechat.freenode.net)\n> might also be useful for inspiration in coming up with a proposal.\n\nI meant to link to webchat.freenode.net.  But\nhttps://kiwiirc.com/nextclient/ may have been a better link to use\nanyway.\n\nThanks and sorry for the noise,\nJonathan\n"},{"id":"351821","messageId":"20180706213239.GA867@flurp.local","threadId":"48834","inReplyTo":"20180706211600.GB6195@aiede.svl.corp.google.com","subject":"Re: de-alphabetizing the documentation","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2018-07-06T21:32:39Z","receivedAt":"2018-07-06T21:32:51Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Jul 06, 2018 at 02:16:00PM -0700, Jonathan Nieder wrote:\n> Frederick Eaton wrote:\n> > I wonder if someone familiar with Git could list the commands in an\n> > order which makes more sense for learning, for example in the order in\n> > which they were invented by Git developers,\n> \n> Alas, there are plenty of \"Main porcelain commands\", and I think that\n> is where your question comes from.  It would be nicer to list just five\n> to start, say.\n\n\"git help\" makes some attempt at narrowing the list of porcelain\ncommands likely to be used on an everyday basis (and it categorizes\nthe list by general activity). Of the 21 commands listed, I use 14-16\nin pretty much every development session, so \"git help\" might be a\ngood starting place for someone trying to figure out which commands to\nstudy, or for someone wishing to help focus the documentation a bit\nmore for beginners.\n\n--- >8 ---\n$ git help\nusage: git ...\n\nThese are common Git commands used in various situations:\n\nstart a working area (see also: git help tutorial)\n   clone      Clone a repository into a new directory\n   init       Create an empty Git repository or reinitialize an existing one\n\nwork on the current change (see also: git help everyday)\n   add        Add file contents to the index\n   mv         Move or rename a file, a directory, or a symlink\n   reset      Reset current HEAD to the specified state\n   rm         Remove files from the working tree and from the index\n\nexamine the history and state (see also: git help revisions)\n   bisect     Use binary search to find the commit that introduced a bug\n   grep       Print lines matching a pattern\n   log        Show commit logs\n   show       Show various types of objects\n   status     Show the working tree status\n\ngrow, mark and tweak your common history\n   branch     List, create, or delete branches\n   checkout   Switch branches or restore working tree files\n   commit     Record changes to the repository\n   diff       Show changes between commits, commit and working tree, etc\n   merge      Join two or more development histories together\n   rebase     Reapply commits on top of another base tip\n   tag        Create, list, delete or verify a tag object signed with GPG\n\ncollaborate (see also: git help workflows)\n   fetch      Download objects and refs from another repository\n   pull       Fetch from and integrate with another repository or a local branch\n   push       Update remote refs along with associated objects\n\n'git help -a' and 'git help -g' list available subcommands and some\nconcept guides. See 'git help <command>' or 'git help <concept>'\nto read about a specific subcommand or concept.\n--- >8 ---\n"},{"id":"351833","messageId":"20180706232147.GF6343@ofb.net","threadId":"48834","inReplyTo":"20180706213239.GA867@flurp.local","subject":"Re: de-alphabetizing the documentation","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2018-07-06T23:21:47Z","receivedAt":"2018-07-06T23:23:02Z","isPatch":false,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Thank you Jonathan for signaling your willingness to adopt the\ndocumentation philosophy I suggested. That's a quite valuable first\nstep. Unfortunately my contribution will have to be limited for the\nmoment to making this suggestion, as I am extraordinarily busy. I hope\nit will not be too burdensome to add this item to your TODO list and\nkeep it there until a willing volunteer comes along.\n\nFor what it's worth, I made extensive changes to the Arch Wiki Git\narticle back in 2015, following an initial attempt of mine to\nunderstand various tutorials. It was the most prominent wiki-based Git\ndocumentation I could find at the time. The article has of course seen\nnumerous improvements since then.\n\nI don't think that it's really important to find a \"best\" ordering for\ncommands or glossary terms; it's more a matter of finding someone who\nis willing to take responsibility for choosing a reasonable ordering.\nPresumably the head maintainer of this project could delegate the task\nto a qualified volunteer, not a newbie like myself but not necessarily\nsomeone with expert knowledge either. It's too bad that a policy of\nnot listing things alphabetically wasn't adopted from the beginning of\nthis project, but I guess that's life.\n\nThanks Eric for the pointer to \"git help\". This does indeed provide a\nfiner and better grouping than the man-page (but it also looks like\nanother candidate for de-alphabetization...!).\n\nMany thanks,\n\nFrederick\n\nOn Fri, Jul 06, 2018 at 02:18:28PM -0700, Jonathan Nieder wrote:\n> Jonathan Nieder wrote:\n> \n> > Ideas?  If you start with a proposal, we're happy to help refine it.\n> > People in the #git channel on irc.freenode.net (wechat.freenode.net)\n> > might also be useful for inspiration in coming up with a proposal.\n> \n> I meant to link to webchat.freenode.net.  But\n> https://kiwiirc.com/nextclient/ may have been a better link to use\n> anyway.\n> \n> Thanks and sorry for the noise,\n> Jonathan\n> \n\nOn Fri, Jul 06, 2018 at 05:32:39PM -0400, Eric Sunshine wrote:\n> On Fri, Jul 06, 2018 at 02:16:00PM -0700, Jonathan Nieder wrote:\n> > Frederick Eaton wrote:\n> > > I wonder if someone familiar with Git could list the commands in an\n> > > order which makes more sense for learning, for example in the order in\n> > > which they were invented by Git developers,\n> > \n> > Alas, there are plenty of \"Main porcelain commands\", and I think that\n> > is where your question comes from.  It would be nicer to list just five\n> > to start, say.\n> \n> \"git help\" makes some attempt at narrowing the list of porcelain\n> commands likely to be used on an everyday basis (and it categorizes\n> the list by general activity). Of the 21 commands listed, I use 14-16\n> in pretty much every development session, so \"git help\" might be a\n> good starting place for someone trying to figure out which commands to\n> study, or for someone wishing to help focus the documentation a bit\n> more for beginners.\n> \n> --- >8 ---\n> $ git help\n> usage: git ...\n> \n> These are common Git commands used in various situations:\n> \n> start a working area (see also: git help tutorial)\n>    clone      Clone a repository into a new directory\n>    init       Create an empty Git repository or reinitialize an existing one\n> \n> work on the current change (see also: git help everyday)\n>    add        Add file contents to the index\n>    mv         Move or rename a file, a directory, or a symlink\n>    reset      Reset current HEAD to the specified state\n>    rm         Remove files from the working tree and from the index\n> \n> examine the history and state (see also: git help revisions)\n>    bisect     Use binary search to find the commit that introduced a bug\n>    grep       Print lines matching a pattern\n>    log        Show commit logs\n>    show       Show various types of objects\n>    status     Show the working tree status\n> \n> grow, mark and tweak your common history\n>    branch     List, create, or delete branches\n>    checkout   Switch branches or restore working tree files\n>    commit     Record changes to the repository\n>    diff       Show changes between commits, commit and working tree, etc\n>    merge      Join two or more development histories together\n>    rebase     Reapply commits on top of another base tip\n>    tag        Create, list, delete or verify a tag object signed with GPG\n> \n> collaborate (see also: git help workflows)\n>    fetch      Download objects and refs from another repository\n>    pull       Fetch from and integrate with another repository or a local branch\n>    push       Update remote refs along with associated objects\n> \n> 'git help -a' and 'git help -g' list available subcommands and some\n> concept guides. See 'git help <command>' or 'git help <concept>'\n> to read about a specific subcommand or concept.\n> --- >8 ---\n> \n\n"},{"id":"351834","messageId":"20180706234715.GA81694@aiede.svl.corp.google.com","threadId":"48834","inReplyTo":"20180706232147.GF6343@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-07-06T23:47:15Z","receivedAt":"2018-07-06T23:47:26Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nFrederick Eaton wrote:\n\n>       Unfortunately my contribution will have to be limited for the\n> moment to making this suggestion, as I am extraordinarily busy. I hope\n> it will not be too burdensome to add this item to your TODO list and\n> keep it there until a willing volunteer comes along.\n\nNo problem.  If you have time to contribute later, we can wait. :)\n\n> For what it's worth, I made extensive changes to the Arch Wiki Git\n> article back in 2015, following an initial attempt of mine to\n> understand various tutorials. It was the most prominent wiki-based Git\n> documentation I could find at the time. The article has of course seen\n> numerous improvements since then.\n\nFor reference: https://wiki.archlinux.org/index.php/git\n\n> I don't think that it's really important to find a \"best\" ordering for\n> commands or glossary terms; it's more a matter of finding someone who\n> is willing to take responsibility for choosing a reasonable ordering.\n> Presumably the head maintainer of this project could delegate the task\n> to a qualified volunteer, not a newbie like myself but not necessarily\n> someone with expert knowledge either.\n\nI'd have to say, when I compare the troubles a new user and a\nlong-timer would run into, I conclude that the long-timers would be\nmore likely to produce worse documentation.  It is very difficult to\nremember how new users see things.  The ideal skill set in fact has\nnothing to do with level of Git expertise: to produce a good result, a\ngood technical writer would ask the right questions to gather\ninformation from the experts and then test their documentation on\nnewcomers until it works well.\n\nBased on the work you've described already having done, it sounds like\nyou'd be an ideal person to get this going, if you find yourself with\ntime for it.\n\n>                                       It's too bad that a policy of\n> not listing things alphabetically wasn't adopted from the beginning of\n> this project, but I guess that's life.\n\nFrom this thread I've been convinced that for this kind of reference\ndocument, alphabetical organization within each section is a good\norganization, provided each section is small enough (as in \"git help\"\noutput).\n\nI'm also a fan of non reference documentation that can use a narrative\nordering instead (like \"git help core-tutorial\", except with more\nmodern commands).\n\n> Thanks Eric for the pointer to \"git help\". This does indeed provide a\n> finer and better grouping than the man-page (but it also looks like\n> another candidate for de-alphabetization...!).\n\nIndeed, copying that organization over from \"git help\" to the git(1)\nmanpage may be a good step for any interested people overhearing this\nconversation.\n\nAs a first step, how about making git(1) recommend \"git help\", like\nthis?  It already recommends giteveryday(7) but the more interactive\nfirst command might be useful for some people.\n\nThoughts?  Improvements?\n\n-- >8 --\nSubject: git doc: recommend \"git help\" as a starting point\n\nThe list of subcommands described in git(1) can be overwhelming.\nEncourage newcomers to run \"git help\" to get a shorter list of\ncommands as a starting point.\n\nBased on a suggestion by Frederick Eaton.\n\nSigned-off-by: Jonathan Nieder <jrnieder@gmail.com>\n---\n Documentation/git.txt | 9 ++++++---\n 1 file changed, 6 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex dba7f0c18e..0149ce9af0 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -23,9 +23,12 @@ unusually rich command set that provides both high-level operations\n and full access to internals.\n \n See linkgit:gittutorial[7] to get started, then see\n-linkgit:giteveryday[7] for a useful minimum set of\n-commands.  The link:user-manual.html[Git User's Manual] has a more\n-in-depth introduction.\n+linkgit:giteveryday[7] and run\n+\n+    git help\n+\n+for a useful minimum set of commands.  The link:user-manual.html[Git\n+User's Manual] has a more in-depth introduction.\n \n After you mastered the basic concepts, you can come back to this\n page to learn what commands Git offers.  You can learn more about\n-- \n2.18.0.203.gfac676dfb9\n\n"},{"id":"351837","messageId":"20180707042534.GC3546@thunk.org","threadId":"48834","inReplyTo":"20180706232147.GF6343@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"Theodore Y. Ts'o","fromEmail":"tytso@mit.edu","sentAt":"2018-07-07T04:25:34Z","receivedAt":"2018-07-07T04:25:46Z","isPatch":false,"sender":{"key":"tytso@mit.edu","avatar":"https://avatars.githubusercontent.com/u/51416?v=4"},"body":"On Fri, Jul 06, 2018 at 04:21:47PM -0700, frederik@ofb.net wrote:\n> I don't think that it's really important to find a \"best\" ordering for\n> commands or glossary terms; it's more a matter of finding someone who\n> is willing to take responsibility for choosing a reasonable ordering.\n> Presumably the head maintainer of this project could delegate the task\n> to a qualified volunteer, not a newbie like myself but not necessarily\n> someone with expert knowledge either. It's too bad that a policy of\n> not listing things alphabetically wasn't adopted from the beginning of\n> this project, but I guess that's life.\n\nThat wasn't that portion of the man page, for better or for worse.  We\ncan debate whethher using a non-alphabetical order would be better or\nworse for everyone; personally, I think the much better pointer is at\nthe very beginning of the git man page, which points people at \"man\ngittutorial\" and \"man giteveryday\".\n\nIt seems to me that for your stated goal, \"git everyday\" has a good\nlist of commands that people should learn, complete with a proposed\nworkflow.\n\nThat's probably the biggest stumbling block of finding an ideal\nordering.  What's reasonable really depends on your workflow, and\nthere are many different workflows depending on what a particular\ndeveloper is trying to do.  Consider carpentry; for some use cases, a\nscrewdriver is an absolutely critical tool.  For others, they might\nnever use it, and instead almost exclusively join two pieces of woods\nusing mortise and tenon joint.  Others might use a butt joint, plus\nglue and nails.  All of these different techniques can be used to make\na wooden box, and they all involve a very different set of tools.\n\nRegards,\n\n\t\t\t\t\t- Ted\n"},{"id":"351863","messageId":"20180708010926.GK6343@ofb.net","threadId":"48834","inReplyTo":"20180706234715.GA81694@aiede.svl.corp.google.com","subject":"Re: de-alphabetizing the documentation","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2018-07-08T01:09:26Z","receivedAt":"2018-07-08T01:10:46Z","isPatch":false,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Hi Jonathan,\n\nIf it's really just a matter of needing someone with a newcomer's\nperspective, then I'd be happy to look over the ordering of the git\nsubcommands. You can run the command I provided to glean the frequency\nof each subcommand from your shell history, I'll look over the output\nand see if the ordering makes sense to me, and then you or someone\nelse can rearrange the manual page to list the subcommands in this\norder. Is that a suitable plan?\n\nThanks,\n\nFrederick\n\nOn Fri, Jul 06, 2018 at 04:47:15PM -0700, Jonathan Nieder wrote:\n> Hi,\n> \n> Frederick Eaton wrote:\n> \n> >       Unfortunately my contribution will have to be limited for the\n> > moment to making this suggestion, as I am extraordinarily busy. I hope\n> > it will not be too burdensome to add this item to your TODO list and\n> > keep it there until a willing volunteer comes along.\n> \n> No problem.  If you have time to contribute later, we can wait. :)\n> \n> > For what it's worth, I made extensive changes to the Arch Wiki Git\n> > article back in 2015, following an initial attempt of mine to\n> > understand various tutorials. It was the most prominent wiki-based Git\n> > documentation I could find at the time. The article has of course seen\n> > numerous improvements since then.\n> \n> For reference: https://wiki.archlinux.org/index.php/git\n> \n> > I don't think that it's really important to find a \"best\" ordering for\n> > commands or glossary terms; it's more a matter of finding someone who\n> > is willing to take responsibility for choosing a reasonable ordering.\n> > Presumably the head maintainer of this project could delegate the task\n> > to a qualified volunteer, not a newbie like myself but not necessarily\n> > someone with expert knowledge either.\n> \n> I'd have to say, when I compare the troubles a new user and a\n> long-timer would run into, I conclude that the long-timers would be\n> more likely to produce worse documentation.  It is very difficult to\n> remember how new users see things.  The ideal skill set in fact has\n> nothing to do with level of Git expertise: to produce a good result, a\n> good technical writer would ask the right questions to gather\n> information from the experts and then test their documentation on\n> newcomers until it works well.\n> \n> Based on the work you've described already having done, it sounds like\n> you'd be an ideal person to get this going, if you find yourself with\n> time for it.\n> \n> >                                       It's too bad that a policy of\n> > not listing things alphabetically wasn't adopted from the beginning of\n> > this project, but I guess that's life.\n> \n> From this thread I've been convinced that for this kind of reference\n> document, alphabetical organization within each section is a good\n> organization, provided each section is small enough (as in \"git help\"\n> output).\n> \n> I'm also a fan of non reference documentation that can use a narrative\n> ordering instead (like \"git help core-tutorial\", except with more\n> modern commands).\n> \n> > Thanks Eric for the pointer to \"git help\". This does indeed provide a\n> > finer and better grouping than the man-page (but it also looks like\n> > another candidate for de-alphabetization...!).\n> \n> Indeed, copying that organization over from \"git help\" to the git(1)\n> manpage may be a good step for any interested people overhearing this\n> conversation.\n> \n> As a first step, how about making git(1) recommend \"git help\", like\n> this?  It already recommends giteveryday(7) but the more interactive\n> first command might be useful for some people.\n> \n> Thoughts?  Improvements?\n> \n> -- >8 --\n> Subject: git doc: recommend \"git help\" as a starting point\n> \n> The list of subcommands described in git(1) can be overwhelming.\n> Encourage newcomers to run \"git help\" to get a shorter list of\n> commands as a starting point.\n> \n> Based on a suggestion by Frederick Eaton.\n> \n> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>\n> ---\n>  Documentation/git.txt | 9 ++++++---\n>  1 file changed, 6 insertions(+), 3 deletions(-)\n> \n> diff --git a/Documentation/git.txt b/Documentation/git.txt\n> index dba7f0c18e..0149ce9af0 100644\n> --- a/Documentation/git.txt\n> +++ b/Documentation/git.txt\n> @@ -23,9 +23,12 @@ unusually rich command set that provides both high-level operations\n>  and full access to internals.\n>  \n>  See linkgit:gittutorial[7] to get started, then see\n> -linkgit:giteveryday[7] for a useful minimum set of\n> -commands.  The link:user-manual.html[Git User's Manual] has a more\n> -in-depth introduction.\n> +linkgit:giteveryday[7] and run\n> +\n> +    git help\n> +\n> +for a useful minimum set of commands.  The link:user-manual.html[Git\n> +User's Manual] has a more in-depth introduction.\n>  \n>  After you mastered the basic concepts, you can come back to this\n>  page to learn what commands Git offers.  You can learn more about\n> -- \n> 2.18.0.203.gfac676dfb9\n> \n"},{"id":"353520","messageId":"20180724195217.GA9366@ofb.net","threadId":"48834","inReplyTo":"20180708010926.GK6343@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2018-07-24T19:52:18Z","receivedAt":"2018-07-24T19:54:07Z","isPatch":false,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Hello Jonathan,\n\nThank you for replying to me earlier. I just wanted to follow up on\nthis thread. Did you decide not to go with my proposal?\n\nNext week I should have time to send you a patch with the manual page\nreordered... although, unless you have a special 'diff' which can\ndetect when text has been moved from one place to another, I'm\nguessing it would take you even longer to check the validity of the\npatch than it would for me to create it.\n\nHowever, I'm happy to do this or whatever other small projects you\nwould like to delegate as far as improving readability of your\ndocumentation. I just need to know what is likely to be accepted.\n\nThanks,\n\nFrederick\n\nOn Sat, Jul 07, 2018 at 06:09:26PM -0700, frederik@ofb.net wrote:\n> Hi Jonathan,\n> \n> If it's really just a matter of needing someone with a newcomer's\n> perspective, then I'd be happy to look over the ordering of the git\n> subcommands. You can run the command I provided to glean the frequency\n> of each subcommand from your shell history, I'll look over the output\n> and see if the ordering makes sense to me, and then you or someone\n> else can rearrange the manual page to list the subcommands in this\n> order. Is that a suitable plan?\n> \n> Thanks,\n> \n> Frederick\n> \n> On Fri, Jul 06, 2018 at 04:47:15PM -0700, Jonathan Nieder wrote:\n> > Hi,\n> > \n> > Frederick Eaton wrote:\n> > \n> > >       Unfortunately my contribution will have to be limited for the\n> > > moment to making this suggestion, as I am extraordinarily busy. I hope\n> > > it will not be too burdensome to add this item to your TODO list and\n> > > keep it there until a willing volunteer comes along.\n> > \n> > No problem.  If you have time to contribute later, we can wait. :)\n> > \n> > > For what it's worth, I made extensive changes to the Arch Wiki Git\n> > > article back in 2015, following an initial attempt of mine to\n> > > understand various tutorials. It was the most prominent wiki-based Git\n> > > documentation I could find at the time. The article has of course seen\n> > > numerous improvements since then.\n> > \n> > For reference: https://wiki.archlinux.org/index.php/git\n> > \n> > > I don't think that it's really important to find a \"best\" ordering for\n> > > commands or glossary terms; it's more a matter of finding someone who\n> > > is willing to take responsibility for choosing a reasonable ordering.\n> > > Presumably the head maintainer of this project could delegate the task\n> > > to a qualified volunteer, not a newbie like myself but not necessarily\n> > > someone with expert knowledge either.\n> > \n> > I'd have to say, when I compare the troubles a new user and a\n> > long-timer would run into, I conclude that the long-timers would be\n> > more likely to produce worse documentation.  It is very difficult to\n> > remember how new users see things.  The ideal skill set in fact has\n> > nothing to do with level of Git expertise: to produce a good result, a\n> > good technical writer would ask the right questions to gather\n> > information from the experts and then test their documentation on\n> > newcomers until it works well.\n> > \n> > Based on the work you've described already having done, it sounds like\n> > you'd be an ideal person to get this going, if you find yourself with\n> > time for it.\n> > \n> > >                                       It's too bad that a policy of\n> > > not listing things alphabetically wasn't adopted from the beginning of\n> > > this project, but I guess that's life.\n> > \n> > From this thread I've been convinced that for this kind of reference\n> > document, alphabetical organization within each section is a good\n> > organization, provided each section is small enough (as in \"git help\"\n> > output).\n> > \n> > I'm also a fan of non reference documentation that can use a narrative\n> > ordering instead (like \"git help core-tutorial\", except with more\n> > modern commands).\n> > \n> > > Thanks Eric for the pointer to \"git help\". This does indeed provide a\n> > > finer and better grouping than the man-page (but it also looks like\n> > > another candidate for de-alphabetization...!).\n> > \n> > Indeed, copying that organization over from \"git help\" to the git(1)\n> > manpage may be a good step for any interested people overhearing this\n> > conversation.\n> > \n> > As a first step, how about making git(1) recommend \"git help\", like\n> > this?  It already recommends giteveryday(7) but the more interactive\n> > first command might be useful for some people.\n> > \n> > Thoughts?  Improvements?\n> > \n> > -- >8 --\n> > Subject: git doc: recommend \"git help\" as a starting point\n> > \n> > The list of subcommands described in git(1) can be overwhelming.\n> > Encourage newcomers to run \"git help\" to get a shorter list of\n> > commands as a starting point.\n> > \n> > Based on a suggestion by Frederick Eaton.\n> > \n> > Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>\n> > ---\n> >  Documentation/git.txt | 9 ++++++---\n> >  1 file changed, 6 insertions(+), 3 deletions(-)\n> > \n> > diff --git a/Documentation/git.txt b/Documentation/git.txt\n> > index dba7f0c18e..0149ce9af0 100644\n> > --- a/Documentation/git.txt\n> > +++ b/Documentation/git.txt\n> > @@ -23,9 +23,12 @@ unusually rich command set that provides both high-level operations\n> >  and full access to internals.\n> >  \n> >  See linkgit:gittutorial[7] to get started, then see\n> > -linkgit:giteveryday[7] for a useful minimum set of\n> > -commands.  The link:user-manual.html[Git User's Manual] has a more\n> > -in-depth introduction.\n> > +linkgit:giteveryday[7] and run\n> > +\n> > +    git help\n> > +\n> > +for a useful minimum set of commands.  The link:user-manual.html[Git\n> > +User's Manual] has a more in-depth introduction.\n> >  \n> >  After you mastered the basic concepts, you can come back to this\n> >  page to learn what commands Git offers.  You can learn more about\n> > -- \n> > 2.18.0.203.gfac676dfb9\n> > \n> \n"},{"id":"353528","messageId":"20180724211146.GB136514@aiede.svl.corp.google.com","threadId":"48834","inReplyTo":"20180724195217.GA9366@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2018-07-24T21:11:46Z","receivedAt":"2018-07-24T21:11:51Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi,\n\nfrederik@ofb.net wrote:\n\n> Next week I should have time to send you a patch with the manual page\n> reordered...\n\nYay!\n\n>               although, unless you have a special 'diff' which can\n> detect when text has been moved from one place to another, I'm\n> guessing it would take you even longer to check the validity of the\n> patch than it would for me to create it.\n\nFortunately we have \"git diff --color-moved\".\n\n> However, I'm happy to do this or whatever other small projects you\n> would like to delegate as far as improving readability of your\n> documentation. I just need to know what is likely to be accepted.\n\nStarting with this one seems fine.  Maybe people on list will have\nideas for followups on top, or maybe you'll have ideas for ways others\ncan help you, or both. ;-)\n\nThanks again,\nJonathan\n"},{"id":"355228","messageId":"20180811023036.GA19208@ofb.net","threadId":"48834","inReplyTo":"20180724211146.GB136514@aiede.svl.corp.google.com","subject":"Re: de-alphabetizing the documentation","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2018-08-11T02:30:36Z","receivedAt":"2018-08-11T02:33:07Z","isPatch":false,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Hi Jonathan and Git developers,\n\nI poked around today and figured out how to reorder the command\nlistings in the manual page, they are taken from git/command-list.txt\nso I just reorder the lines in that file (after disabling sorting in\ngit/Documentation/cmd-list.perl).\n\nI haven't reordered the whole list yet. I could only get one computer\nfriend to send me his subcommand frequencies from his shell history. I\nreordered the commands partly based on that, and partly based on their\norder of occurrence in the various tutorial man pages.\n\nI'm attaching a preliminary patch (not ready to be applied) just to\nmake sure this is going to be OK with the maintainer (who is the\nmaintainer?) before I continue. I made it with \"git format-patch\".\n\nIt seems fairly straightforward, but please let me know if there are\nany problems. By the way, the command I used to check that the new\ncommand list contains all the original commands is as follows:\n\ndiff =(sort command-list.txt | grep -v '^#') =(git cat-file blob e1c26c1bb7e618f6f372d9a568e7cab75612d2db | grep -v '^#' | sort)\n\nThanks,\n\nFrederick\n\nOn Tue, Jul 24, 2018 at 02:11:46PM -0700, Jonathan Nieder wrote:\n> Hi,\n> \n> frederik@ofb.net wrote:\n> \n> > Next week I should have time to send you a patch with the manual page\n> > reordered...\n> \n> Yay!\n> \n> >               although, unless you have a special 'diff' which can\n> > detect when text has been moved from one place to another, I'm\n> > guessing it would take you even longer to check the validity of the\n> > patch than it would for me to create it.\n> \n> Fortunately we have \"git diff --color-moved\".\n> \n> > However, I'm happy to do this or whatever other small projects you\n> > would like to delegate as far as improving readability of your\n> > documentation. I just need to know what is likely to be accepted.\n> \n> Starting with this one seems fine.  Maybe people on list will have\n> ideas for followups on top, or maybe you'll have ideas for ways others\n> can help you, or both. ;-)\n> \n> Thanks again,\n> Jonathan\n> \n\n\nFrom 7aabe1060eabee16fac239ce49b8f9749be11adb Mon Sep 17 00:00:00 2001\nFrom: Frederick Eaton <frederik@ofb.net>\nDate: Fri, 10 Aug 2018 18:54:28 -0700\nSubject: [PATCH] First test of command reordering\n\n---\n Documentation/cmd-list.perl |   2 +-\n command-list.txt            | 107 +++++++++++++++++++++++++-------------------\n 2 files changed, 61 insertions(+), 48 deletions(-)\n\ndiff --git a/Documentation/cmd-list.perl b/Documentation/cmd-list.perl\nindex 5aa73cfe4..62c32f58d 100755\n--- a/Documentation/cmd-list.perl\n+++ b/Documentation/cmd-list.perl\n@@ -43,7 +43,7 @@ sub format_one {\n }\n \n my %cmds = ();\n-for (sort <>) {\n+for (<>) {\n \tnext if /^#/;\n \n \tchomp;\ndiff --git a/command-list.txt b/command-list.txt\nindex e1c26c1bb..94a15fd42 100644\n--- a/command-list.txt\n+++ b/command-list.txt\n@@ -43,35 +43,83 @@\n # specified here, which can only have \"guide\" attribute and nothing\n # else.\n #\n+# August 2018: The list has been reordered for didactic purposes,\n+# basically according to approximate usefulness / frequency of use /\n+# order of use. This is to make it possible for a beginner to read the\n+# manual page \"straight through\" and see the most important commands\n+# first, rather than getting them in alphabetical order. Please\n+# consider this when adding new commands.\n+#\n ### command list (do not change this line, also do not change alignment)\n # command name                          category [category] [category]\n+# From tutorial\n+git-help                                ancillaryinterrogators          complete\n+git-config                              ancillarymanipulators           complete\n+git-clone                               mainporcelain           init\n+git-init                                mainporcelain           init\n git-add                                 mainporcelain           worktree\n-git-am                                  mainporcelain\n+git-commit                              mainporcelain           history\n+git-diff                                mainporcelain           history\n+git-status                              mainporcelain           info\n+git-log                                 mainporcelain           info\n+git-branch                              mainporcelain           history\n+git-checkout                            mainporcelain           history\n+git-merge                               mainporcelain           history\n+gitk                                    mainporcelain\n+git-pull                                mainporcelain           remote\n+git-fetch                               mainporcelain           remote\n+# From frequencies\n+git-grep                                mainporcelain           info\n+git-show                                mainporcelain           info\n+git-push                                mainporcelain           remote\n+git-submodule                           mainporcelain\n+git-reset                               mainporcelain           worktree\n+git-cherry-pick                         mainporcelain\n+git-tag                                 mainporcelain           history\n+git-clean                               mainporcelain\n+# From tutorial NEXT STEPS\n+git-format-patch                        mainporcelain\n+git-bisect                              mainporcelain           info\n+gitworkflows                            guide\n+giteveryday                             guide\n+gitcvs-migration                        guide\n+# From tutorial-2 (+ls-remote)\n+git-cat-file                            plumbinginterrogators\n+git-ls-tree                             plumbinginterrogators\n+git-ls-files                            plumbinginterrogators\n+git-ls-remote                           plumbinginterrogators\n+gitcore-tutorial                        guide\n+gitglossary                             guide\n+# From gitcore-tutorial\n+git-update-index                        plumbingmanipulators\n+git-diff-files                          plumbinginterrogators\n+git-write-tree                          plumbingmanipulators\n+git-read-tree                           plumbingmanipulators\n+git-checkout-index                      plumbingmanipulators\n+git-show-branch                         ancillaryinterrogators          complete\n+git-name-rev                            plumbinginterrogators\n+git-merge-index                         plumbingmanipulators\n+git-repack                              ancillarymanipulators           complete\n+git-prune-packed                        plumbingmanipulators\n+git-update-server-info                  synchingrepositories\n+git-prune                               ancillarymanipulators\n+git-cherry                              ancillaryinterrogators          complete\n+# Remaining unsorted (alphabetized) commands\n git-annotate                            ancillaryinterrogators\n git-apply                               plumbingmanipulators            complete\n git-archimport                          foreignscminterface\n git-archive                             mainporcelain\n-git-bisect                              mainporcelain           info\n git-blame                               ancillaryinterrogators          complete\n-git-branch                              mainporcelain           history\n+git-am                                  mainporcelain\n git-bundle                              mainporcelain\n-git-cat-file                            plumbinginterrogators\n git-check-attr                          purehelpers\n git-check-ignore                        purehelpers\n git-check-mailmap                       purehelpers\n-git-checkout                            mainporcelain           history\n-git-checkout-index                      plumbingmanipulators\n git-check-ref-format                    purehelpers\n-git-cherry                              ancillaryinterrogators          complete\n-git-cherry-pick                         mainporcelain\n git-citool                              mainporcelain\n-git-clean                               mainporcelain\n-git-clone                               mainporcelain           init\n git-column                              purehelpers\n-git-commit                              mainporcelain           history\n git-commit-graph                        plumbingmanipulators\n git-commit-tree                         plumbingmanipulators\n-git-config                              ancillarymanipulators           complete\n git-count-objects                       ancillaryinterrogators\n git-credential                          purehelpers\n git-credential-cache                    purehelpers\n@@ -81,52 +129,37 @@ git-cvsimport                           foreignscminterface\n git-cvsserver                           foreignscminterface\n git-daemon                              synchingrepositories\n git-describe                            mainporcelain\n-git-diff                                mainporcelain           history\n-git-diff-files                          plumbinginterrogators\n git-diff-index                          plumbinginterrogators\n git-diff-tree                           plumbinginterrogators\n git-difftool                            ancillaryinterrogators          complete\n git-fast-export                         ancillarymanipulators\n git-fast-import                         ancillarymanipulators\n-git-fetch                               mainporcelain           remote\n git-fetch-pack                          synchingrepositories\n git-filter-branch                       ancillarymanipulators\n git-fmt-merge-msg                       purehelpers\n git-for-each-ref                        plumbinginterrogators\n-git-format-patch                        mainporcelain\n git-fsck                                ancillaryinterrogators          complete\n git-gc                                  mainporcelain\n git-get-tar-commit-id                   ancillaryinterrogators\n-git-grep                                mainporcelain           info\n git-gui                                 mainporcelain\n git-hash-object                         plumbingmanipulators\n-git-help                                ancillaryinterrogators          complete\n git-http-backend                        synchingrepositories\n git-http-fetch                          synchelpers\n git-http-push                           synchelpers\n git-imap-send                           foreignscminterface\n git-index-pack                          plumbingmanipulators\n-git-init                                mainporcelain           init\n git-instaweb                            ancillaryinterrogators          complete\n git-interpret-trailers                  purehelpers\n-gitk                                    mainporcelain\n-git-log                                 mainporcelain           info\n-git-ls-files                            plumbinginterrogators\n-git-ls-remote                           plumbinginterrogators\n-git-ls-tree                             plumbinginterrogators\n git-mailinfo                            purehelpers\n git-mailsplit                           purehelpers\n-git-merge                               mainporcelain           history\n git-merge-base                          plumbinginterrogators\n git-merge-file                          plumbingmanipulators\n-git-merge-index                         plumbingmanipulators\n git-merge-one-file                      purehelpers\n git-mergetool                           ancillarymanipulators           complete\n git-merge-tree                          ancillaryinterrogators\n git-mktag                               plumbingmanipulators\n git-mktree                              plumbingmanipulators\n git-mv                                  mainporcelain           worktree\n-git-name-rev                            plumbinginterrogators\n git-notes                               mainporcelain\n git-p4                                  foreignscminterface\n git-pack-objects                        plumbingmanipulators\n@@ -134,21 +167,14 @@ git-pack-redundant                      plumbinginterrogators\n git-pack-refs                           ancillarymanipulators\n git-parse-remote                        synchelpers\n git-patch-id                            purehelpers\n-git-prune                               ancillarymanipulators\n-git-prune-packed                        plumbingmanipulators\n-git-pull                                mainporcelain           remote\n-git-push                                mainporcelain           remote\n git-quiltimport                         foreignscminterface\n-git-read-tree                           plumbingmanipulators\n git-rebase                              mainporcelain           history\n git-receive-pack                        synchelpers\n git-reflog                              ancillarymanipulators           complete\n git-remote                              ancillarymanipulators           complete\n-git-repack                              ancillarymanipulators           complete\n git-replace                             ancillarymanipulators           complete\n git-request-pull                        foreignscminterface             complete\n git-rerere                              ancillaryinterrogators\n-git-reset                               mainporcelain           worktree\n git-revert                              mainporcelain\n git-rev-list                            plumbinginterrogators\n git-rev-parse                           ancillaryinterrogators\n@@ -157,25 +183,18 @@ git-send-email                          foreignscminterface             complete\n git-send-pack                           synchingrepositories\n git-shell                               synchelpers\n git-shortlog                            mainporcelain\n-git-show                                mainporcelain           info\n-git-show-branch                         ancillaryinterrogators          complete\n git-show-index                          plumbinginterrogators\n git-show-ref                            plumbinginterrogators\n git-sh-i18n                             purehelpers\n git-sh-setup                            purehelpers\n git-stash                               mainporcelain\n git-stage                                                               complete\n-git-status                              mainporcelain           info\n git-stripspace                          purehelpers\n-git-submodule                           mainporcelain\n git-svn                                 foreignscminterface\n git-symbolic-ref                        plumbingmanipulators\n-git-tag                                 mainporcelain           history\n git-unpack-file                         plumbinginterrogators\n git-unpack-objects                      plumbingmanipulators\n-git-update-index                        plumbingmanipulators\n git-update-ref                          plumbingmanipulators\n-git-update-server-info                  synchingrepositories\n git-upload-archive                      synchelpers\n git-upload-pack                         synchelpers\n git-var                                 plumbinginterrogators\n@@ -185,14 +204,9 @@ git-verify-tag                          ancillaryinterrogators\n gitweb                                  ancillaryinterrogators\n git-whatchanged                         ancillaryinterrogators          complete\n git-worktree                            mainporcelain\n-git-write-tree                          plumbingmanipulators\n gitattributes                           guide\n gitcli                                  guide\n-gitcore-tutorial                        guide\n-gitcvs-migration                        guide\n gitdiffcore                             guide\n-giteveryday                             guide\n-gitglossary                             guide\n githooks                                guide\n gitignore                               guide\n gitmodules                              guide\n@@ -201,4 +215,3 @@ gitrepository-layout                    guide\n gitrevisions                            guide\n gittutorial-2                           guide\n gittutorial                             guide\n-gitworkflows                            guide\n-- \n2.13.1\n\n\n\nGIT(1)                            Git Manual                            GIT(1)\n\nNAME\n       git - the stupid content tracker\n\nSYNOPSIS\n       git [--version] [--help] [-C <path>] [-c <name>=<value>]\n           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\n           [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]\n           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\n           [--super-prefix=<path>]\n           <command> [<args>]\n\nDESCRIPTION\n       Git is a fast, scalable, distributed revision control system with an\n       unusually rich command set that provides both high-level operations and\n       full access to internals.\n\n       See gittutorial(7) to get started, then see giteveryday(7) for a useful\n       minimum set of commands. The Git User's Manual[1] has a more in-depth\n       introduction.\n\n       After you mastered the basic concepts, you can come back to this page\n       to learn what commands Git offers. You can learn more about individual\n       Git commands with \"git help command\". gitcli(7) manual page gives you\n       an overview of the command-line command syntax.\n\n       A formatted and hyperlinked copy of the latest Git documentation can be\n       viewed at https://git.github.io/htmldocs/git.html.\n\nOPTIONS\n       --version\n           Prints the Git suite version that the git program came from.\n\n       --help\n           Prints the synopsis and a list of the most commonly used commands.\n           If the option --all or -a is given then all available commands are\n           printed. If a Git command is named this option will bring up the\n           manual page for that command.\n\n           Other options are available to control how the manual page is\n           displayed. See git-help(1) for more information, because git --help\n           ...  is converted internally into git help ....\n\n       -C <path>\n           Run as if git was started in <path> instead of the current working\n           directory. When multiple -C options are given, each subsequent\n           non-absolute -C <path> is interpreted relative to the preceding -C\n           <path>.\n\n           This option affects options that expect path name like --git-dir\n           and --work-tree in that their interpretations of the path names\n           would be made relative to the working directory caused by the -C\n           option. For example the following invocations are equivalent:\n\n               git --git-dir=a.git --work-tree=b -C c status\n               git --git-dir=c/a.git --work-tree=c/b status\n\n       -c <name>=<value>\n           Pass a configuration parameter to the command. The value given will\n           override values from configuration files. The <name> is expected in\n           the same format as listed by git config (subkeys separated by\n           dots).\n\n           Note that omitting the = in git -c foo.bar ...  is allowed and sets\n           foo.bar to the boolean true value (just like [foo]bar would in a\n           config file). Including the equals but with an empty value (like\n           git -c foo.bar= ...) sets foo.bar to the empty string which git\n           config --bool will convert to false.\n\n       --exec-path[=<path>]\n           Path to wherever your core Git programs are installed. This can\n           also be controlled by setting the GIT_EXEC_PATH environment\n           variable. If no path is given, git will print the current setting\n           and then exit.\n\n       --html-path\n           Print the path, without trailing slash, where Git's HTML\n           documentation is installed and exit.\n\n       --man-path\n           Print the manpath (see man(1)) for the man pages for this version\n           of Git and exit.\n\n       --info-path\n           Print the path where the Info files documenting this version of Git\n           are installed and exit.\n\n       -p, --paginate\n           Pipe all output into less (or if set, $PAGER) if standard output is\n           a terminal. This overrides the pager.<cmd> configuration options\n           (see the \"Configuration Mechanism\" section below).\n\n       -P, --no-pager\n           Do not pipe Git output into a pager.\n\n       --git-dir=<path>\n           Set the path to the repository. This can also be controlled by\n           setting the GIT_DIR environment variable. It can be an absolute\n           path or relative path to current working directory.\n\n       --work-tree=<path>\n           Set the path to the working tree. It can be an absolute path or a\n           path relative to the current working directory. This can also be\n           controlled by setting the GIT_WORK_TREE environment variable and\n           the core.worktree configuration variable (see core.worktree in git-\n           config(1) for a more detailed discussion).\n\n       --namespace=<path>\n           Set the Git namespace. See gitnamespaces(7) for more details.\n           Equivalent to setting the GIT_NAMESPACE environment variable.\n\n       --super-prefix=<path>\n           Currently for internal use only. Set a prefix which gives a path\n           from above a repository down to its root. One use is to give\n           submodules context about the superproject that invoked it.\n\n       --bare\n           Treat the repository as a bare repository. If GIT_DIR environment\n           is not set, it is set to the current working directory.\n\n       --no-replace-objects\n           Do not use replacement refs to replace Git objects. See git-\n           replace(1) for more information.\n\n       --literal-pathspecs\n           Treat pathspecs literally (i.e. no globbing, no pathspec magic).\n           This is equivalent to setting the GIT_LITERAL_PATHSPECS environment\n           variable to 1.\n\n       --glob-pathspecs\n           Add \"glob\" magic to all pathspec. This is equivalent to setting the\n           GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on\n           individual pathspecs can be done using pathspec magic \":(literal)\"\n\n       --noglob-pathspecs\n           Add \"literal\" magic to all pathspec. This is equivalent to setting\n           the GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling\n           globbing on individual pathspecs can be done using pathspec magic\n           \":(glob)\"\n\n       --icase-pathspecs\n           Add \"icase\" magic to all pathspec. This is equivalent to setting\n           the GIT_ICASE_PATHSPECS environment variable to 1.\n\n       --no-optional-locks\n           Do not perform optional operations that require locks. This is\n           equivalent to setting the GIT_OPTIONAL_LOCKS to 0.\n\n       --list-cmds=group[,group...]\n           List commands by group. This is an internal/experimental option and\n           may change or be removed in the future. Supported groups are:\n           builtins, parseopt (builtin commands that use parse-options), main\n           (all commands in libexec directory), others (all other commands in\n           $PATH that have git- prefix), list-<category> (see categories in\n           command-list.txt), nohelpers (exclude helper commands), alias and\n           config (retrieve command list from config variable\n           completion.commands)\n\nGIT COMMANDS\n       We divide Git into high level (\"porcelain\") commands and low level\n       (\"plumbing\") commands.\n\nHIGH-LEVEL COMMANDS (PORCELAIN)\n       We separate the porcelain commands into the main commands and some\n       ancillary user utilities.\n\n   Main porcelain commands\n       git-clone(1)\n           Clone a repository into a new directory.\n\n       git-init(1)\n           Create an empty Git repository or reinitialize an existing one.\n\n       git-add(1)\n           Add file contents to the index.\n\n       git-commit(1)\n           Record changes to the repository.\n\n       git-diff(1)\n           Show changes between commits, commit and working tree, etc.\n\n       git-status(1)\n           Show the working tree status.\n\n       git-log(1)\n           Show commit logs.\n\n       git-branch(1)\n           List, create, or delete branches.\n\n       git-checkout(1)\n           Switch branches or restore working tree files.\n\n       git-merge(1)\n           Join two or more development histories together.\n\n       gitk(1)\n           The Git repository browser.\n\n       git-pull(1)\n           Fetch from and integrate with another repository or a local branch.\n\n       git-fetch(1)\n           Download objects and refs from another repository.\n\n       git-grep(1)\n           Print lines matching a pattern.\n\n       git-show(1)\n           Show various types of objects.\n\n       git-push(1)\n           Update remote refs along with associated objects.\n\n       git-submodule(1)\n           Initialize, update or inspect submodules.\n\n       git-reset(1)\n           Reset current HEAD to the specified state.\n\n       git-cherry-pick(1)\n           Apply the changes introduced by some existing commits.\n\n       git-tag(1)\n           Create, list, delete or verify a tag object signed with GPG.\n\n       git-clean(1)\n           Remove untracked files from the working tree.\n\n       git-format-patch(1)\n           Prepare patches for e-mail submission.\n\n       git-bisect(1)\n           Use binary search to find the commit that introduced a bug.\n\n       git-archive(1)\n           Create an archive of files from a named tree.\n\n       git-am(1)\n           Apply a series of patches from a mailbox.\n\n       git-bundle(1)\n           Move objects and refs by archive.\n\n       git-citool(1)\n           Graphical alternative to git-commit.\n\n       git-describe(1)\n           Give an object a human readable name based on an available ref.\n\n       git-gc(1)\n           Cleanup unnecessary files and optimize the local repository.\n\n       git-gui(1)\n           A portable graphical interface to Git.\n\n       git-mv(1)\n           Move or rename a file, a directory, or a symlink.\n\n       git-notes(1)\n           Add or inspect object notes.\n\n       git-rebase(1)\n           Reapply commits on top of another base tip.\n\n       git-revert(1)\n           Revert some existing commits.\n\n       git-rm(1)\n           Remove files from the working tree and from the index.\n\n       git-shortlog(1)\n           Summarize git log output.\n\n       git-stash(1)\n           Stash the changes in a dirty working directory away.\n\n       git-worktree(1)\n           Manage multiple working trees.\n\n   Ancillary Commands\n       Manipulators:\n\n       git-config(1)\n           Get and set repository or global options.\n\n       git-repack(1)\n           Pack unpacked objects in a repository.\n\n       git-prune(1)\n           Prune all unreachable objects from the object database.\n\n       git-fast-export(1)\n           Git data exporter.\n\n       git-fast-import(1)\n           Backend for fast Git data importers.\n\n       git-filter-branch(1)\n           Rewrite branches.\n\n       git-mergetool(1)\n           Run merge conflict resolution tools to resolve merge conflicts.\n\n       git-pack-refs(1)\n           Pack heads and tags for efficient repository access.\n\n       git-reflog(1)\n           Manage reflog information.\n\n       git-remote(1)\n           Manage set of tracked repositories.\n\n       git-replace(1)\n           Create, list, delete refs to replace objects.\n\n       Interrogators:\n\n       git-help(1)\n           Display help information about Git.\n\n       git-show-branch(1)\n           Show branches and their commits.\n\n       git-cherry(1)\n           Find commits yet to be applied to upstream.\n\n       git-annotate(1)\n           Annotate file lines with commit information.\n\n       git-blame(1)\n           Show what revision and author last modified each line of a file.\n\n       git-count-objects(1)\n           Count unpacked number of objects and their disk consumption.\n\n       git-difftool(1)\n           Show changes using common diff tools.\n\n       git-fsck(1)\n           Verifies the connectivity and validity of the objects in the\n           database.\n\n       git-get-tar-commit-id(1)\n           Extract commit ID from an archive created using git-archive.\n\n       git-instaweb(1)\n           Instantly browse your working repository in gitweb.\n\n       git-merge-tree(1)\n           Show three-way merge without touching index.\n\n       git-rerere(1)\n           Reuse recorded resolution of conflicted merges.\n\n       git-rev-parse(1)\n           Pick out and massage parameters.\n\n       git-verify-commit(1)\n           Check the GPG signature of commits.\n\n       git-verify-tag(1)\n           Check the GPG signature of tags.\n\n       gitweb(1)\n           Git web interface (web frontend to Git repositories).\n\n       git-whatchanged(1)\n           Show logs with difference each commit introduces.\n\n   Interacting with Others\n       These commands are to interact with foreign SCM and with other people\n       via patch over e-mail.\n\n       git-archimport(1)\n           Import an Arch repository into Git.\n\n       git-cvsexportcommit(1)\n           Export a single commit to a CVS checkout.\n\n       git-cvsimport(1)\n           Salvage your data out of another SCM people love to hate.\n\n       git-cvsserver(1)\n           A CVS server emulator for Git.\n\n       git-imap-send(1)\n           Send a collection of patches from stdin to an IMAP folder.\n\n       git-p4(1)\n           Import from and submit to Perforce repositories.\n\n       git-quiltimport(1)\n           Applies a quilt patchset onto the current branch.\n\n       git-request-pull(1)\n           Generates a summary of pending changes.\n\n       git-send-email(1)\n           Send a collection of patches as emails.\n\n       git-svn(1)\n           Bidirectional operation between a Subversion repository and Git.\n\nLOW-LEVEL COMMANDS (PLUMBING)\n       Although Git includes its own porcelain layer, its low-level commands\n       are sufficient to support development of alternative porcelains.\n       Developers of such porcelains might start by reading about git-update-\n       index(1) and git-read-tree(1).\n\n       The interface (input, output, set of options and the semantics) to\n       these low-level commands are meant to be a lot more stable than\n       Porcelain level commands, because these commands are primarily for\n       scripted use. The interface to Porcelain commands on the other hand are\n       subject to change in order to improve the end user experience.\n\n       The following description divides the low-level commands into commands\n       that manipulate objects (in the repository, index, and working tree),\n       commands that interrogate and compare objects, and commands that move\n       objects and references between repositories.\n\n   Manipulation commands\n       git-update-index(1)\n           Register file contents in the working tree to the index.\n\n       git-write-tree(1)\n           Create a tree object from the current index.\n\n       git-read-tree(1)\n           Reads tree information into the index.\n\n       git-checkout-index(1)\n           Copy files from the index to the working tree.\n\n       git-merge-index(1)\n           Run a merge for files needing merging.\n\n       git-prune-packed(1)\n           Remove extra objects that are already in pack files.\n\n       git-apply(1)\n           Apply a patch to files and/or to the index.\n\n       git-commit-graph(1)\n           Write and verify Git commit graph files.\n\n       git-commit-tree(1)\n           Create a new commit object.\n\n       git-hash-object(1)\n           Compute object ID and optionally creates a blob from a file.\n\n       git-index-pack(1)\n           Build pack index file for an existing packed archive.\n\n       git-merge-file(1)\n           Run a three-way file merge.\n\n       git-mktag(1)\n           Creates a tag object.\n\n       git-mktree(1)\n           Build a tree-object from ls-tree formatted text.\n\n       git-pack-objects(1)\n           Create a packed archive of objects.\n\n       git-symbolic-ref(1)\n           Read, modify and delete symbolic refs.\n\n       git-unpack-objects(1)\n           Unpack objects from a packed archive.\n\n       git-update-ref(1)\n           Update the object name stored in a ref safely.\n\n   Interrogation commands\n       git-cat-file(1)\n           Provide content or type and size information for repository\n           objects.\n\n       git-ls-tree(1)\n           List the contents of a tree object.\n\n       git-ls-files(1)\n           Show information about files in the index and the working tree.\n\n       git-ls-remote(1)\n           List references in a remote repository.\n\n       git-diff-files(1)\n           Compares files in the working tree and the index.\n\n       git-name-rev(1)\n           Find symbolic names for given revs.\n\n       git-diff-index(1)\n           Compare a tree to the working tree or index.\n\n       git-diff-tree(1)\n           Compares the content and mode of blobs found via two tree objects.\n\n       git-for-each-ref(1)\n           Output information on each ref.\n\n       git-merge-base(1)\n           Find as good common ancestors as possible for a merge.\n\n       git-pack-redundant(1)\n           Find redundant pack files.\n\n       git-rev-list(1)\n           Lists commit objects in reverse chronological order.\n\n       git-show-index(1)\n           Show packed archive index.\n\n       git-show-ref(1)\n           List references in a local repository.\n\n       git-unpack-file(1)\n           Creates a temporary file with a blob's contents.\n\n       git-var(1)\n           Show a Git logical variable.\n\n       git-verify-pack(1)\n           Validate packed Git archive files.\n\n       In general, the interrogate commands do not touch the files in the\n       working tree.\n\n   Synching repositories\n       git-update-server-info(1)\n           Update auxiliary info file to help dumb servers.\n\n       git-daemon(1)\n           A really simple server for Git repositories.\n\n       git-fetch-pack(1)\n           Receive missing objects from another repository.\n\n       git-http-backend(1)\n           Server side implementation of Git over HTTP.\n\n       git-send-pack(1)\n           Push objects over Git protocol to another repository.\n\n       The following are helper commands used by the above; end users\n       typically do not use them directly.\n\n       git-http-fetch(1)\n           Download from a remote Git repository via HTTP.\n\n       git-http-push(1)\n           Push objects over HTTP/DAV to another repository.\n\n       git-parse-remote(1)\n           Routines to help parsing remote repository access parameters.\n\n       git-receive-pack(1)\n           Receive what is pushed into the repository.\n\n       git-shell(1)\n           Restricted login shell for Git-only SSH access.\n\n       git-upload-archive(1)\n           Send archive back to git-archive.\n\n       git-upload-pack(1)\n           Send objects packed back to git-fetch-pack.\n\n   Internal helper commands\n       These are internal helper commands used by other commands; end users\n       typically do not use them directly.\n\n       git-check-attr(1)\n           Display gitattributes information.\n\n       git-check-ignore(1)\n           Debug gitignore / exclude files.\n\n       git-check-mailmap(1)\n           Show canonical names and email addresses of contacts.\n\n       git-check-ref-format(1)\n           Ensures that a reference name is well formed.\n\n       git-column(1)\n           Display data in columns.\n\n       git-credential(1)\n           Retrieve and store user credentials.\n\n       git-credential-cache(1)\n           Helper to temporarily store passwords in memory.\n\n       git-credential-store(1)\n           Helper to store credentials on disk.\n\n       git-fmt-merge-msg(1)\n           Produce a merge commit message.\n\n       git-interpret-trailers(1)\n           add or parse structured information in commit messages.\n\n       git-mailinfo(1)\n           Extracts patch and authorship from a single e-mail message.\n\n       git-mailsplit(1)\n           Simple UNIX mbox splitter program.\n\n       git-merge-one-file(1)\n           The standard helper program to use with git-merge-index.\n\n       git-patch-id(1)\n           Compute unique ID for a patch.\n\n       git-sh-i18n(1)\n           Git's i18n setup code for shell scripts.\n\n       git-sh-setup(1)\n           Common Git shell script setup code.\n\n       git-stripspace(1)\n           Remove unnecessary whitespace.\n\nCONFIGURATION MECHANISM\n       Git uses a simple text format to store customizations that are per\n       repository and are per user. Such a configuration file may look like\n       this:\n\n           #\n           # A '#' or ';' character indicates a comment.\n           #\n\n           ; core variables\n           [core]\n                   ; Don't trust file modes\n                   filemode = false\n\n           ; user identity\n           [user]\n                   name = \"Junio C Hamano\"\n                   email = \"gitster@pobox.com\"\n\n       Various commands read from the configuration file and adjust their\n       operation accordingly. See git-config(1) for a list and more details\n       about the configuration mechanism.\n\nIDENTIFIER TERMINOLOGY\n       <object>\n           Indicates the object name for any type of object.\n\n       <blob>\n           Indicates a blob object name.\n\n       <tree>\n           Indicates a tree object name.\n\n       <commit>\n           Indicates a commit object name.\n\n       <tree-ish>\n           Indicates a tree, commit or tag object name. A command that takes a\n           <tree-ish> argument ultimately wants to operate on a <tree> object\n           but automatically dereferences <commit> and <tag> objects that\n           point at a <tree>.\n\n       <commit-ish>\n           Indicates a commit or tag object name. A command that takes a\n           <commit-ish> argument ultimately wants to operate on a <commit>\n           object but automatically dereferences <tag> objects that point at a\n           <commit>.\n\n       <type>\n           Indicates that an object type is required. Currently one of: blob,\n           tree, commit, or tag.\n\n       <file>\n           Indicates a filename - almost always relative to the root of the\n           tree structure GIT_INDEX_FILE describes.\n\nSYMBOLIC IDENTIFIERS\n       Any Git command accepting any <object> can also use the following\n       symbolic notation:\n\n       HEAD\n           indicates the head of the current branch.\n\n       <tag>\n           a valid tag name (i.e. a refs/tags/<tag> reference).\n\n       <head>\n           a valid head name (i.e. a refs/heads/<head> reference).\n\n       For a more complete list of ways to spell object names, see \"SPECIFYING\n       REVISIONS\" section in gitrevisions(7).\n\nFILE/DIRECTORY STRUCTURE\n       Please see the gitrepository-layout(5) document.\n\n       Read githooks(5) for more details about each hook.\n\n       Higher level SCMs may provide and manage additional information in the\n       $GIT_DIR.\n\nTERMINOLOGY\n       Please see gitglossary(7).\n\nENVIRONMENT VARIABLES\n       Various Git commands use the following environment variables:\n\n   The Git Repository\n       These environment variables apply to all core Git commands. Nb: it is\n       worth noting that they may be used/overridden by SCMS sitting above Git\n       so take care if using a foreign front-end.\n\n       GIT_INDEX_FILE\n           This environment allows the specification of an alternate index\n           file. If not specified, the default of $GIT_DIR/index is used.\n\n       GIT_INDEX_VERSION\n           This environment variable allows the specification of an index\n           version for new repositories. It won't affect existing index files.\n           By default index file version 2 or 3 is used. See git-update-\n           index(1) for more information.\n\n       GIT_OBJECT_DIRECTORY\n           If the object storage directory is specified via this environment\n           variable then the sha1 directories are created underneath -\n           otherwise the default $GIT_DIR/objects directory is used.\n\n       GIT_ALTERNATE_OBJECT_DIRECTORIES\n           Due to the immutable nature of Git objects, old objects can be\n           archived into shared, read-only directories. This variable\n           specifies a \":\" separated (on Windows \";\" separated) list of Git\n           object directories which can be used to search for Git objects. New\n           objects will not be written to these directories.\n\n               Entries that begin with `\"` (double-quote) will be interpreted\n               as C-style quoted paths, removing leading and trailing\n               double-quotes and respecting backslash escapes. E.g., the value\n               `\"path-with-\\\"-and-:-in-it\":vanilla-path` has two paths:\n               `path-with-\"-and-:-in-it` and `vanilla-path`.\n\n       GIT_DIR\n           If the GIT_DIR environment variable is set then it specifies a path\n           to use instead of the default .git for the base of the repository.\n           The --git-dir command-line option also sets this value.\n\n       GIT_WORK_TREE\n           Set the path to the root of the working tree. This can also be\n           controlled by the --work-tree command-line option and the\n           core.worktree configuration variable.\n\n       GIT_NAMESPACE\n           Set the Git namespace; see gitnamespaces(7) for details. The\n           --namespace command-line option also sets this value.\n\n       GIT_CEILING_DIRECTORIES\n           This should be a colon-separated list of absolute paths. If set, it\n           is a list of directories that Git should not chdir up into while\n           looking for a repository directory (useful for excluding\n           slow-loading network directories). It will not exclude the current\n           working directory or a GIT_DIR set on the command line or in the\n           environment. Normally, Git has to read the entries in this list and\n           resolve any symlink that might be present in order to compare them\n           with the current directory. However, if even this access is slow,\n           you can add an empty entry to the list to tell Git that the\n           subsequent entries are not symlinks and needn't be resolved; e.g.,\n           GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink.\n\n       GIT_DISCOVERY_ACROSS_FILESYSTEM\n           When run in a directory that does not have \".git\" repository\n           directory, Git tries to find such a directory in the parent\n           directories to find the top of the working tree, but by default it\n           does not cross filesystem boundaries. This environment variable can\n           be set to true to tell Git not to stop at filesystem boundaries.\n           Like GIT_CEILING_DIRECTORIES, this will not affect an explicit\n           repository directory set via GIT_DIR or on the command line.\n\n       GIT_COMMON_DIR\n           If this variable is set to a path, non-worktree files that are\n           normally in $GIT_DIR will be taken from this path instead.\n           Worktree-specific files such as HEAD or index are taken from\n           $GIT_DIR. See gitrepository-layout(5) and git-worktree(1) for\n           details. This variable has lower precedence than other path\n           variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...\n\n   Git Commits\n       GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME,\n       GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, EMAIL\n           see git-commit-tree(1)\n\n   Git Diffs\n       GIT_DIFF_OPTS\n           Only valid setting is \"--unified=??\" or \"-u??\" to set the number of\n           context lines shown when a unified diff is created. This takes\n           precedence over any \"-U\" or \"--unified\" option value passed on the\n           Git diff command line.\n\n       GIT_EXTERNAL_DIFF\n           When the environment variable GIT_EXTERNAL_DIFF is set, the program\n           named by it is called, instead of the diff invocation described\n           above. For a path that is added, removed, or modified,\n           GIT_EXTERNAL_DIFF is called with 7 parameters:\n\n               path old-file old-hex old-mode new-file new-hex new-mode\n\n           where:\n\n       <old|new>-file\n           are files GIT_EXTERNAL_DIFF can use to read the contents of\n           <old|new>,\n\n       <old|new>-hex\n           are the 40-hexdigit SHA-1 hashes,\n\n       <old|new>-mode\n           are the octal representation of the file modes.\n\n           The file parameters can point at the user's working file (e.g.\n           new-file in \"git-diff-files\"), /dev/null (e.g.  old-file when a new\n           file is added), or a temporary file (e.g.  old-file in the index).\n           GIT_EXTERNAL_DIFF should not worry about unlinking the temporary\n           file --- it is removed when GIT_EXTERNAL_DIFF exits.\n\n           For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1\n           parameter, <path>.\n\n           For each path GIT_EXTERNAL_DIFF is called, two environment\n           variables, GIT_DIFF_PATH_COUNTER and GIT_DIFF_PATH_TOTAL are set.\n\n       GIT_DIFF_PATH_COUNTER\n           A 1-based counter incremented by one for every path.\n\n       GIT_DIFF_PATH_TOTAL\n           The total number of paths.\n\n   other\n       GIT_MERGE_VERBOSITY\n           A number controlling the amount of output shown by the recursive\n           merge strategy. Overrides merge.verbosity. See git-merge(1)\n\n       GIT_PAGER\n           This environment variable overrides $PAGER. If it is set to an\n           empty string or to the value \"cat\", Git will not launch a pager.\n           See also the core.pager option in git-config(1).\n\n       GIT_EDITOR\n           This environment variable overrides $EDITOR and $VISUAL. It is used\n           by several Git commands when, on interactive mode, an editor is to\n           be launched. See also git-var(1) and the core.editor option in git-\n           config(1).\n\n       GIT_SSH, GIT_SSH_COMMAND\n           If either of these environment variables is set then git fetch and\n           git push will use the specified command instead of ssh when they\n           need to connect to a remote system. The command-line parameters\n           passed to the configured command are determined by the ssh variant.\n           See ssh.variant option in git-config(1) for details.\n\n       + $GIT_SSH_COMMAND takes precedence over $GIT_SSH, and is interpreted\n       by the shell, which allows additional arguments to be included.\n       $GIT_SSH on the other hand must be just the path to a program (which\n       can be a wrapper shell script, if additional arguments are needed).\n\n       + Usually it is easier to configure any desired options through your\n       personal .ssh/config file. Please consult your ssh documentation for\n       further details.\n\n       GIT_SSH_VARIANT\n           If this environment variable is set, it overrides Git's\n           autodetection whether GIT_SSH/GIT_SSH_COMMAND/core.sshCommand refer\n           to OpenSSH, plink or tortoiseplink. This variable overrides the\n           config setting ssh.variant that serves the same purpose.\n\n       GIT_ASKPASS\n           If this environment variable is set, then Git commands which need\n           to acquire passwords or passphrases (e.g. for HTTP or IMAP\n           authentication) will call this program with a suitable prompt as\n           command-line argument and read the password from its STDOUT. See\n           also the core.askPass option in git-config(1).\n\n       GIT_TERMINAL_PROMPT\n           If this environment variable is set to 0, git will not prompt on\n           the terminal (e.g., when asking for HTTP authentication).\n\n       GIT_CONFIG_NOSYSTEM\n           Whether to skip reading settings from the system-wide\n           $(prefix)/etc/gitconfig file. This environment variable can be used\n           along with $HOME and $XDG_CONFIG_HOME to create a predictable\n           environment for a picky script, or you can set it temporarily to\n           avoid using a buggy /etc/gitconfig file while waiting for someone\n           with sufficient permissions to fix it.\n\n       GIT_FLUSH\n           If this environment variable is set to \"1\", then commands such as\n           git blame (in incremental mode), git rev-list, git log, git\n           check-attr and git check-ignore will force a flush of the output\n           stream after each record have been flushed. If this variable is set\n           to \"0\", the output of these commands will be done using completely\n           buffered I/O. If this environment variable is not set, Git will\n           choose buffered or record-oriented flushing based on whether stdout\n           appears to be redirected to a file or not.\n\n       GIT_TRACE\n           Enables general trace messages, e.g. alias expansion, built-in\n           command execution and external command execution.\n\n           If this variable is set to \"1\", \"2\" or \"true\" (comparison is case\n           insensitive), trace messages will be printed to stderr.\n\n           If the variable is set to an integer value greater than 2 and lower\n           than 10 (strictly) then Git will interpret this value as an open\n           file descriptor and will try to write the trace messages into this\n           file descriptor.\n\n           Alternatively, if the variable is set to an absolute path (starting\n           with a / character), Git will interpret this as a file path and\n           will try to write the trace messages into it.\n\n           Unsetting the variable, or setting it to empty, \"0\" or \"false\"\n           (case insensitive) disables trace messages.\n\n       GIT_TRACE_FSMONITOR\n           Enables trace messages for the filesystem monitor extension. See\n           GIT_TRACE for available trace output options.\n\n       GIT_TRACE_PACK_ACCESS\n           Enables trace messages for all accesses to any packs. For each\n           access, the pack file name and an offset in the pack is recorded.\n           This may be helpful for troubleshooting some pack-related\n           performance problems. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_PACKET\n           Enables trace messages for all packets coming in or out of a given\n           program. This can help with debugging object negotiation or other\n           protocol issues. Tracing is turned off at a packet starting with\n           \"PACK\" (but see GIT_TRACE_PACKFILE below). See GIT_TRACE for\n           available trace output options.\n\n       GIT_TRACE_PACKFILE\n           Enables tracing of packfiles sent or received by a given program.\n           Unlike other trace output, this trace is verbatim: no headers, and\n           no quoting of binary data. You almost certainly want to direct into\n           a file (e.g., GIT_TRACE_PACKFILE=/tmp/my.pack) rather than\n           displaying it on the terminal or mixing it with other trace output.\n\n           Note that this is currently only implemented for the client side of\n           clones and fetches.\n\n       GIT_TRACE_PERFORMANCE\n           Enables performance related trace messages, e.g. total execution\n           time of each Git command. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_SETUP\n           Enables trace messages printing the .git, working tree and current\n           working directory after Git has completed its setup phase. See\n           GIT_TRACE for available trace output options.\n\n       GIT_TRACE_SHALLOW\n           Enables trace messages that can help debugging fetching / cloning\n           of shallow repositories. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_CURL\n           Enables a curl full trace dump of all incoming and outgoing data,\n           including descriptive information, of the git transport protocol.\n           This is similar to doing curl --trace-ascii on the command line.\n           This option overrides setting the GIT_CURL_VERBOSE environment\n           variable. See GIT_TRACE for available trace output options.\n\n       GIT_TRACE_CURL_NO_DATA\n           When a curl trace is enabled (see GIT_TRACE_CURL above), do not\n           dump data (that is, only dump info lines and headers).\n\n       GIT_REDACT_COOKIES\n           This can be set to a comma-separated list of strings. When a curl\n           trace is enabled (see GIT_TRACE_CURL above), whenever a \"Cookies:\"\n           header sent by the client is dumped, values of cookies whose key is\n           in that list (case-sensitive) are redacted.\n\n       GIT_LITERAL_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs\n           literally, rather than as glob patterns. For example, running\n           GIT_LITERAL_PATHSPECS=1 git log -- '*.c' will search for commits\n           that touch the path *.c, not any paths that the glob *.c matches.\n           You might want this if you are feeding literal paths to Git (e.g.,\n           paths previously given to you by git ls-tree, --raw diff output,\n           etc).\n\n       GIT_GLOB_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           glob patterns (aka \"glob\" magic).\n\n       GIT_NOGLOB_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           literal (aka \"literal\" magic).\n\n       GIT_ICASE_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           case-insensitive.\n\n       GIT_REFLOG_ACTION\n           When a ref is updated, reflog entries are created to keep track of\n           the reason why the ref was updated (which is typically the name of\n           the high-level command that updated the ref), in addition to the\n           old and new values of the ref. A scripted Porcelain command can use\n           set_reflog_action helper function in git-sh-setup to set its name\n           to this variable when it is invoked as the top level command by the\n           end user, to be recorded in the body of the reflog.\n\n       GIT_REF_PARANOIA\n           If set to 1, include broken or badly named refs when iterating over\n           lists of refs. In a normal, non-corrupted repository, this does\n           nothing. However, enabling it may help git to detect and abort some\n           operations in the presence of broken refs. Git sets this variable\n           automatically when performing destructive operations like git-\n           prune(1). You should not need to set it yourself unless you want to\n           be paranoid about making sure an operation has touched every ref\n           (e.g., because you are cloning a repository to make a backup).\n\n       GIT_ALLOW_PROTOCOL\n           If set to a colon-separated list of protocols, behave as if\n           protocol.allow is set to never, and each of the listed protocols\n           has protocol.<name>.allow set to always (overriding any existing\n           configuration). In other words, any protocol not mentioned will be\n           disallowed (i.e., this is a whitelist, not a blacklist). See the\n           description of protocol.allow in git-config(1) for more details.\n\n       GIT_PROTOCOL_FROM_USER\n           Set to 0 to prevent protocols used by fetch/push/clone which are\n           configured to the user state. This is useful to restrict recursive\n           submodule initialization from an untrusted repository or for\n           programs which feed potentially-untrusted URLS to git commands. See\n           git-config(1) for more details.\n\n       GIT_PROTOCOL\n           For internal use only. Used in handshaking the wire protocol.\n           Contains a colon : separated list of keys with optional values\n           key[=value]. Presence of unknown keys and values must be ignored.\n\n       GIT_OPTIONAL_LOCKS\n           If set to 0, Git will complete any requested operation without\n           performing any optional sub-operations that require taking a lock.\n           For example, this will prevent git status from refreshing the index\n           as a side effect. This is useful for processes running in the\n           background which do not want to cause lock contention with other\n           operations on the repository. Defaults to 1.\n\n       GIT_REDIRECT_STDIN, GIT_REDIRECT_STDOUT, GIT_REDIRECT_STDERR\n           Windows-only: allow redirecting the standard input/output/error\n           handles to paths specified by the environment variables. This is\n           particularly useful in multi-threaded applications where the\n           canonical way to pass standard handles via CreateProcess() is not\n           an option because it would require the handles to be marked\n           inheritable (and consequently every spawned process would inherit\n           them, possibly blocking regular Git operations). The primary\n           intended use case is to use named pipes for communication (e.g.\n           \\\\.\\pipe\\my-git-stdin-123).\n\n           Two special values are supported: off will simply close the\n           corresponding standard handle, and if GIT_REDIRECT_STDERR is 2>&1,\n           standard error will be redirected to the same handle as standard\n           output.\n\n       GIT_PRINT_SHA1_ELLIPSIS (deprecated)\n           If set to yes, print an ellipsis following an (abbreviated) SHA-1\n           value. This affects indications of detached HEADs (git-checkout(1))\n           and the raw diff output (git-diff(1)). Printing an ellipsis in the\n           cases mentioned is no longer considered adequate and support for it\n           is likely to be removed in the foreseeable future (along with the\n           variable).\n\nDISCUSSION\n       More detail on the following is available from the Git concepts chapter\n       of the user-manual[2] and gitcore-tutorial(7).\n\n       A Git project normally consists of a working directory with a \".git\"\n       subdirectory at the top level. The .git directory contains, among other\n       things, a compressed object database representing the complete history\n       of the project, an \"index\" file which links that history to the current\n       contents of the working tree, and named pointers into that history such\n       as tags and branch heads.\n\n       The object database contains objects of three main types: blobs, which\n       hold file data; trees, which point to blobs and other trees to build up\n       directory hierarchies; and commits, which each reference a single tree\n       and some number of parent commits.\n\n       The commit, equivalent to what other systems call a \"changeset\" or\n       \"version\", represents a step in the project's history, and each parent\n       represents an immediately preceding step. Commits with more than one\n       parent represent merges of independent lines of development.\n\n       All objects are named by the SHA-1 hash of their contents, normally\n       written as a string of 40 hex digits. Such names are globally unique.\n       The entire history leading up to a commit can be vouched for by signing\n       just that commit. A fourth object type, the tag, is provided for this\n       purpose.\n\n       When first created, objects are stored in individual files, but for\n       efficiency may later be compressed together into \"pack files\".\n\n       Named pointers called refs mark interesting points in history. A ref\n       may contain the SHA-1 name of an object or the name of another ref.\n       Refs with names beginning ref/head/ contain the SHA-1 name of the most\n       recent commit (or \"head\") of a branch under development. SHA-1 names of\n       tags of interest are stored under ref/tags/. A special ref named HEAD\n       contains the name of the currently checked-out branch.\n\n       The index file is initialized with a list of all paths and, for each\n       path, a blob object and a set of attributes. The blob object represents\n       the contents of the file as of the head of the current branch. The\n       attributes (last modified time, size, etc.) are taken from the\n       corresponding file in the working tree. Subsequent changes to the\n       working tree can be found by comparing these attributes. The index may\n       be updated with new content, and new commits may be created from the\n       content stored in the index.\n\n       The index is also capable of storing multiple entries (called \"stages\")\n       for a given pathname. These stages are used to hold the various\n       unmerged version of a file when a merge is in progress.\n\nFURTHER DOCUMENTATION\n       See the references in the \"description\" section to get started using\n       Git. The following is probably more detail than necessary for a\n       first-time user.\n\n       The Git concepts chapter of the user-manual[2] and gitcore-tutorial(7)\n       both provide introductions to the underlying Git architecture.\n\n       See gitworkflows(7) for an overview of recommended workflows.\n\n       See also the howto[3] documents for some useful examples.\n\n       The internals are documented in the Git API documentation[4].\n\n       Users migrating from CVS may also want to read gitcvs-migration(7).\n\nAUTHORS\n       Git was started by Linus Torvalds, and is currently maintained by Junio\n       C Hamano. Numerous contributions have come from the Git mailing list\n       <git@vger.kernel.org[5]>.\n       http://www.openhub.net/p/git/contributors/summary gives you a more\n       complete list of contributors.\n\n       If you have a clone of git.git itself, the output of git-shortlog(1)\n       and git-blame(1) can show you the authors for specific parts of the\n       project.\n\nREPORTING BUGS\n       Report bugs to the Git mailing list <git@vger.kernel.org[5]> where the\n       development and maintenance is primarily done. You do not have to be\n       subscribed to the list to send a message there.\n\n       Issues which are security relevant should be disclosed privately to the\n       Git Security mailing list <git-security@googlegroups.com[6]>.\n\nSEE ALSO\n       gittutorial(7), gittutorial-2(7), giteveryday(7), gitcvs-migration(7),\n       gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User's\n       Manual[1], gitworkflows(7)\n\nGIT\n       Part of the git(1) suite\n\nNOTES\n        1. Git User's Manual\n           file:///home/frederik/pkg-tmp/git/../gitbuild//share/doc/git-doc/user-manual.html\n\n        2. Git concepts chapter of the user-manual\n           file:///home/frederik/pkg-tmp/git/../gitbuild//share/doc/git-doc/user-manual.html#git-concepts\n\n        3. howto\n           file:///home/frederik/pkg-tmp/git/../gitbuild//share/doc/git-doc/howto-index.html\n\n        4. Git API documentation\n           file:///home/frederik/pkg-tmp/git/../gitbuild//share/doc/git-doc/technical/api-index.html\n\n        5. git@vger.kernel.org\n           mailto:git@vger.kernel.org\n\n        6. git-security@googlegroups.com\n           mailto:git-security@googlegroups.com\n\nGit 2.18.0.548.g7aabe1            08/10/2018                            GIT(1)\n\n\n# Command classification list\n# ---------------------------\n# All supported commands, builtin or external, must be described in\n# here. This info is used to list commands in various places. Each\n# command is on one line followed by one or more attributes.\n#\n# The first attribute group is mandatory and indicates the command\n# type. This group includes:\n#\n#   mainporcelain\n#   ancillarymanipulators\n#   ancillaryinterrogators\n#   foreignscminterface\n#   plumbingmanipulators\n#   plumbinginterrogators\n#   synchingrepositories\n#   synchelpers\n#   purehelpers\n#\n# The type names are self explanatory. But if you want to see what\n# command belongs to what group to get a better picture, have a look\n# at \"git\" man page, \"GIT COMMANDS\" section.\n#\n# Commands of type mainporcelain can also optionally have one of these\n# attributes:\n#\n#   init\n#   worktree\n#   info\n#   history\n#   remote\n#\n# These commands are considered \"common\" and will show up in \"git\n# help\" output in groups. Uncommon porcelain commands must not\n# specify any of these attributes.\n#\n# \"complete\" attribute is used to mark that the command should be\n# completable by git-completion.bash. Note that by default,\n# mainporcelain commands are completable so you don't need this\n# attribute.\n#\n# As part of the Git man page list, the man(5/7) guides are also\n# specified here, which can only have \"guide\" attribute and nothing\n# else.\n#\n# August 2018: The list has been reordered for didactic purposes,\n# basically according to approximate usefulness / frequency of use /\n# order of use. This is to make it possible for a beginner to read the\n# manual page \"straight through\" and see the most important commands\n# first, rather than getting them in alphabetical order. Please\n# consider this when adding new commands.\n#\n### command list (do not change this line, also do not change alignment)\n# command name                          category [category] [category]\n# From tutorial\ngit-help                                ancillaryinterrogators          complete\ngit-config                              ancillarymanipulators           complete\ngit-clone                               mainporcelain           init\ngit-init                                mainporcelain           init\ngit-add                                 mainporcelain           worktree\ngit-commit                              mainporcelain           history\ngit-diff                                mainporcelain           history\ngit-status                              mainporcelain           info\ngit-log                                 mainporcelain           info\ngit-branch                              mainporcelain           history\ngit-checkout                            mainporcelain           history\ngit-merge                               mainporcelain           history\ngitk                                    mainporcelain\ngit-pull                                mainporcelain           remote\ngit-fetch                               mainporcelain           remote\n# From frequencies\ngit-grep                                mainporcelain           info\ngit-show                                mainporcelain           info\ngit-push                                mainporcelain           remote\ngit-submodule                           mainporcelain\ngit-reset                               mainporcelain           worktree\ngit-cherry-pick                         mainporcelain\ngit-tag                                 mainporcelain           history\ngit-clean                               mainporcelain\n# From tutorial NEXT STEPS\ngit-format-patch                        mainporcelain\ngit-bisect                              mainporcelain           info\ngitworkflows                            guide\ngiteveryday                             guide\ngitcvs-migration                        guide\n# From tutorial-2 (+ls-remote)\ngit-cat-file                            plumbinginterrogators\ngit-ls-tree                             plumbinginterrogators\ngit-ls-files                            plumbinginterrogators\ngit-ls-remote                           plumbinginterrogators\ngitcore-tutorial                        guide\ngitglossary                             guide\n# From gitcore-tutorial\ngit-update-index                        plumbingmanipulators\ngit-diff-files                          plumbinginterrogators\ngit-write-tree                          plumbingmanipulators\ngit-read-tree                           plumbingmanipulators\ngit-checkout-index                      plumbingmanipulators\ngit-show-branch                         ancillaryinterrogators          complete\ngit-name-rev                            plumbinginterrogators\ngit-merge-index                         plumbingmanipulators\ngit-repack                              ancillarymanipulators           complete\ngit-prune-packed                        plumbingmanipulators\ngit-update-server-info                  synchingrepositories\ngit-prune                               ancillarymanipulators\ngit-cherry                              ancillaryinterrogators          complete\n# Remaining unsorted (alphabetized) commands\ngit-annotate                            ancillaryinterrogators\ngit-apply                               plumbingmanipulators            complete\ngit-archimport                          foreignscminterface\ngit-archive                             mainporcelain\ngit-blame                               ancillaryinterrogators          complete\ngit-am                                  mainporcelain\ngit-bundle                              mainporcelain\ngit-check-attr                          purehelpers\ngit-check-ignore                        purehelpers\ngit-check-mailmap                       purehelpers\ngit-check-ref-format                    purehelpers\ngit-citool                              mainporcelain\ngit-column                              purehelpers\ngit-commit-graph                        plumbingmanipulators\ngit-commit-tree                         plumbingmanipulators\ngit-count-objects                       ancillaryinterrogators\ngit-credential                          purehelpers\ngit-credential-cache                    purehelpers\ngit-credential-store                    purehelpers\ngit-cvsexportcommit                     foreignscminterface\ngit-cvsimport                           foreignscminterface\ngit-cvsserver                           foreignscminterface\ngit-daemon                              synchingrepositories\ngit-describe                            mainporcelain\ngit-diff-index                          plumbinginterrogators\ngit-diff-tree                           plumbinginterrogators\ngit-difftool                            ancillaryinterrogators          complete\ngit-fast-export                         ancillarymanipulators\ngit-fast-import                         ancillarymanipulators\ngit-fetch-pack                          synchingrepositories\ngit-filter-branch                       ancillarymanipulators\ngit-fmt-merge-msg                       purehelpers\ngit-for-each-ref                        plumbinginterrogators\ngit-fsck                                ancillaryinterrogators          complete\ngit-gc                                  mainporcelain\ngit-get-tar-commit-id                   ancillaryinterrogators\ngit-gui                                 mainporcelain\ngit-hash-object                         plumbingmanipulators\ngit-http-backend                        synchingrepositories\ngit-http-fetch                          synchelpers\ngit-http-push                           synchelpers\ngit-imap-send                           foreignscminterface\ngit-index-pack                          plumbingmanipulators\ngit-instaweb                            ancillaryinterrogators          complete\ngit-interpret-trailers                  purehelpers\ngit-mailinfo                            purehelpers\ngit-mailsplit                           purehelpers\ngit-merge-base                          plumbinginterrogators\ngit-merge-file                          plumbingmanipulators\ngit-merge-one-file                      purehelpers\ngit-mergetool                           ancillarymanipulators           complete\ngit-merge-tree                          ancillaryinterrogators\ngit-mktag                               plumbingmanipulators\ngit-mktree                              plumbingmanipulators\ngit-mv                                  mainporcelain           worktree\ngit-notes                               mainporcelain\ngit-p4                                  foreignscminterface\ngit-pack-objects                        plumbingmanipulators\ngit-pack-redundant                      plumbinginterrogators\ngit-pack-refs                           ancillarymanipulators\ngit-parse-remote                        synchelpers\ngit-patch-id                            purehelpers\ngit-quiltimport                         foreignscminterface\ngit-rebase                              mainporcelain           history\ngit-receive-pack                        synchelpers\ngit-reflog                              ancillarymanipulators           complete\ngit-remote                              ancillarymanipulators           complete\ngit-replace                             ancillarymanipulators           complete\ngit-request-pull                        foreignscminterface             complete\ngit-rerere                              ancillaryinterrogators\ngit-revert                              mainporcelain\ngit-rev-list                            plumbinginterrogators\ngit-rev-parse                           ancillaryinterrogators\ngit-rm                                  mainporcelain           worktree\ngit-send-email                          foreignscminterface             complete\ngit-send-pack                           synchingrepositories\ngit-shell                               synchelpers\ngit-shortlog                            mainporcelain\ngit-show-index                          plumbinginterrogators\ngit-show-ref                            plumbinginterrogators\ngit-sh-i18n                             purehelpers\ngit-sh-setup                            purehelpers\ngit-stash                               mainporcelain\ngit-stage                                                               complete\ngit-stripspace                          purehelpers\ngit-svn                                 foreignscminterface\ngit-symbolic-ref                        plumbingmanipulators\ngit-unpack-file                         plumbinginterrogators\ngit-unpack-objects                      plumbingmanipulators\ngit-update-ref                          plumbingmanipulators\ngit-upload-archive                      synchelpers\ngit-upload-pack                         synchelpers\ngit-var                                 plumbinginterrogators\ngit-verify-commit                       ancillaryinterrogators\ngit-verify-pack                         plumbinginterrogators\ngit-verify-tag                          ancillaryinterrogators\ngitweb                                  ancillaryinterrogators\ngit-whatchanged                         ancillaryinterrogators          complete\ngit-worktree                            mainporcelain\ngitattributes                           guide\ngitcli                                  guide\ngitdiffcore                             guide\ngithooks                                guide\ngitignore                               guide\ngitmodules                              guide\ngitnamespaces                           guide\ngitrepository-layout                    guide\ngitrevisions                            guide\ngittutorial-2                           guide\ngittutorial                             guide\n"},{"id":"355429","messageId":"xmqqva8e5dxj.fsf@gitster-ct.c.googlers.com","threadId":"48834","inReplyTo":"20180811023036.GA19208@ofb.net","subject":"Re: de-alphabetizing the documentation","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2018-08-13T18:17:28Z","receivedAt":"2018-08-13T18:17:33Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"frederik@ofb.net writes:\n\n> Hi Jonathan and Git developers,\n>\n> I poked around today and figured out how to reorder the command\n> listings in the manual page, they are taken from git/command-list.txt\n> so I just reorder the lines in that file (after disabling sorting in\n> git/Documentation/cmd-list.perl).\n>\n> I haven't reordered the whole list yet. I could only get one computer\n> friend to send me his subcommand frequencies from his shell history. I\n> reordered the commands partly based on that, and partly based on their\n> order of occurrence in the various tutorial man pages.\n\nThere are two good things about a list that is alphabetical.  One is\nthat you can scan with your eyes and a finger to find what you are\nlooking for more quickly.  The other is that it is mechanical so we\nwon't waste time on bickering whose frequency table is more correct,\nwhether frequency table is a good approach to derive a better order\n(than, say, the order in which the commands appear in an every-day\nworkflow) to begin with.\n\nI would say if we were departing from alphabetical order, we should\nfirst declare that we are *not* looking for the best way to order\nthe list, so that people do not waste too much time bikeshedding.\nInstead what we should aim for is to come up with _an_ order that is\nnot too unreasonable and settle as quickly as we can.\n\nAnd from that point of view, what I saw in new-git.1.out, I found it\nnot so outrageously unreasonable ;-).\n"},{"id":"369654","messageId":"20190219175413.18292-1-frederik@ofb.net","threadId":"48834","inReplyTo":"xmqqva8e5dxj.fsf@gitster-ct.c.googlers.com","subject":"[PATCH 0/1] de-alphabetize command list","fromName":"Frederick Eaton","fromEmail":"frederik@ofb.net","sentAt":"2019-02-19T17:54:12Z","receivedAt":"2019-02-19T18:01:38Z","isPatch":true,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"This is a follow-up to my proposal to de-alphabetize the command\nlistings in the git(1) manual page, from 6 July 2018.\n\nSome projects have manual page items listed in alphabetical order,\nsome don't. As I argued in my proposal, I find it easier to learn from\nmaterial which is not alphabetized. If this patch is accepted, I hope\nthat it will make the Git documentation more accessible to myself and\nothers.\n\nI produced the reordered command list in this patch using several\nsources, as indicated by comments in the new command-list.txt file.\nFirst, all the commands in the main part of \"gittutorial(7)\" appear in\norder, then the commands in giteveryday(7). Then appear additional\ncommands from a friend's shell history, in reverse order of frequency.\nThen gittutorial-2(7), then gitcore-tutorial(7). After that there is a\nlist of \"guides\", followed by about 100 commands not appearing in the\nearlier lists. I kept the guides and the remaining commands in their\ncategory groupings (guide, mainporcelain, ancillarymanipulators,\netc.), but ordered the commands within each category according to my\nown judgment after skimming each manual page.\n\nTo verify that the new list is a permutation of the most recent list,\nI use the following command (it should produce no output and exit 0):\n\n    diff <(git show master:command-list.txt | grep -v '^#' | sort ) <(cat command-list.txt | grep -v '^#' | sort)\n\nNote this patch changes the order of commands appearing in the\ngenerated file \"command-list.h\", which mostly seems to be used by\n\"help.c\". Probably due to the various occurrences of QSORT in\n\"help.c\", I think this reordering has no visible effect. I am willing\nto do any additional testing which may be recommended to ensure that\nthis patch has no undesired consequences.\n\nFrederick Eaton (1):\n  Prioritize list of commands appearing in git(1), via command-list.txt.\n    Don't invoke 'sort' in Documentation/cmd-list.perl.\n\n Documentation/cmd-list.perl |   2 +-\n command-list.txt            | 295 +++++++++++++++++++-----------------\n 2 files changed, 158 insertions(+), 139 deletions(-)\n\n-- \n2.20.1\n\n"},{"id":"369655","messageId":"20190219175413.18292-2-frederik@ofb.net","threadId":"48834","inReplyTo":"xmqqva8e5dxj.fsf@gitster-ct.c.googlers.com","subject":"[PATCH] Prioritize list of commands appearing in git(1), via command-list.txt. Don't invoke 'sort' in Documentation/cmd-list.perl.","fromName":"Frederick Eaton","fromEmail":"frederik@ofb.net","sentAt":"2019-02-19T17:54:13Z","receivedAt":"2019-02-19T18:01:40Z","isPatch":true,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Signed-off-by: Frederick Eaton <frederik@ofb.net>\n---\n Documentation/cmd-list.perl |   2 +-\n command-list.txt            | 295 +++++++++++++++++++-----------------\n 2 files changed, 158 insertions(+), 139 deletions(-)\n\ndiff --git a/Documentation/cmd-list.perl b/Documentation/cmd-list.perl\nindex 5aa73cfe45..62c32f58da 100755\n--- a/Documentation/cmd-list.perl\n+++ b/Documentation/cmd-list.perl\n@@ -43,7 +43,7 @@ sub format_one {\n }\n \n my %cmds = ();\n-for (sort <>) {\n+for (<>) {\n \tnext if /^#/;\n \n \tchomp;\ndiff --git a/command-list.txt b/command-list.txt\nindex 3a9af104b5..fb088dadea 100644\n--- a/command-list.txt\n+++ b/command-list.txt\n@@ -43,164 +43,183 @@\n # specified here, which can only have \"guide\" attribute and nothing\n # else.\n #\n+# February 2019: This list had been sorted alphabetically but has been\n+# reordered to make it easier for people to learn from the main git(1)\n+# manual page. The new ordering is according to approximate usefulness\n+# / frequency of use / order of use, with some grouping by topic. The\n+# idea is to make it possible to read the manual page from beginning\n+# to end and see the most important commands first, rather than\n+# getting them in alphabetical order - in other words, to make the\n+# manual page more like a table of contents and less like an index.\n+# Please consider this when adding new commands.\n+#\n ### command list (do not change this line, also do not change alignment)\n # command name                          category [category] [category]\n+# From gittutorial\n+git-help                                ancillaryinterrogators          complete\n+git-config                              ancillarymanipulators           complete\n+git-clone                               mainporcelain           init\n+git-init                                mainporcelain           init\n git-add                                 mainporcelain           worktree\n-git-am                                  mainporcelain\n-git-annotate                            ancillaryinterrogators\n-git-apply                               plumbingmanipulators            complete\n-git-archimport                          foreignscminterface\n-git-archive                             mainporcelain\n-git-bisect                              mainporcelain           info\n-git-blame                               ancillaryinterrogators          complete\n+git-commit                              mainporcelain           history\n+git-diff                                mainporcelain           history\n+git-status                              mainporcelain           info\n+git-log                                 mainporcelain           info\n git-branch                              mainporcelain           history\n-git-bundle                              mainporcelain\n-git-cat-file                            plumbinginterrogators\n-git-check-attr                          purehelpers\n-git-check-ignore                        purehelpers\n-git-check-mailmap                       purehelpers\n git-checkout                            mainporcelain           history\n+git-merge                               mainporcelain           history\n+gitk                                    mainporcelain\n+git-pull                                mainporcelain           remote\n+git-fetch                               mainporcelain           remote\n+# From tutorial NEXT STEPS\n+git-format-patch                        mainporcelain\n+git-bisect                              mainporcelain           info\n+giteveryday                             guide\n+gitworkflows                            guide\n+gitcvs-migration                        guide\n+# From giteveryday\n+git-reset                               mainporcelain           worktree\n+git-rebase                              mainporcelain           history\n+git-tag                                 mainporcelain           history\n+git-push                                mainporcelain           remote\n+git-send-email                          foreignscminterface             complete\n+git-request-pull                        foreignscminterface             complete\n+git-am                                  mainporcelain\n+git-revert                              mainporcelain\n+git-daemon                              synchingrepositories\n+git-shell                               synchelpers\n+git-http-backend                        synchingrepositories\n+gitweb                                  ancillaryinterrogators\n+# From user feedback\n+git-grep                                mainporcelain           info\n+git-show                                mainporcelain           info\n+git-submodule                           mainporcelain\n+git-cherry-pick                         mainporcelain\n+git-clean                               mainporcelain\n+# From gittutorial-2\n+git-cat-file                            plumbinginterrogators\n+git-ls-tree                             plumbinginterrogators\n+git-ls-files                            plumbinginterrogators\n+gitcore-tutorial                        guide\n+gitglossary                             guide\n+# From gitcore-tutorial\n+git-update-index                        plumbingmanipulators\n+git-diff-files                          plumbinginterrogators\n+git-write-tree                          plumbingmanipulators\n+git-read-tree                           plumbingmanipulators\n git-checkout-index                      plumbingmanipulators\n-git-check-ref-format                    purehelpers\n+git-show-branch                         ancillaryinterrogators          complete\n+git-name-rev                            plumbinginterrogators\n+git-merge-index                         plumbingmanipulators\n+git-repack                              ancillarymanipulators           complete\n+git-prune-packed                        plumbingmanipulators\n+git-update-server-info                  synchingrepositories\n+git-prune                               ancillarymanipulators\n git-cherry                              plumbinginterrogators          complete\n-git-cherry-pick                         mainporcelain\n+# Guides, reordered\n+gittutorial                             guide\n+gittutorial-2                           guide\n+gitrevisions                            guide\n+gitignore                               guide\n+gitcli                                  guide\n+gitrepository-layout                    guide\n+gitdiffcore                             guide\n+gitmodules                              guide\n+githooks                                guide\n+gitnamespaces                           guide\n+gitattributes                           guide\n+# All other commands, sorted by man page category and then by\n+# approximate priority\n+git-stash                               mainporcelain\n+git-rm                                  mainporcelain           worktree\n+git-mv                                  mainporcelain           worktree\n+git-gui                                 mainporcelain\n git-citool                              mainporcelain\n-git-clean                               mainporcelain\n-git-clone                               mainporcelain           init\n-git-column                              purehelpers\n-git-commit                              mainporcelain           history\n-git-commit-graph                        plumbingmanipulators\n-git-commit-tree                         plumbingmanipulators\n-git-config                              ancillarymanipulators           complete\n-git-count-objects                       ancillaryinterrogators\n-git-credential                          purehelpers\n-git-credential-cache                    purehelpers\n-git-credential-store                    purehelpers\n-git-cvsexportcommit                     foreignscminterface\n-git-cvsimport                           foreignscminterface\n-git-cvsserver                           foreignscminterface\n-git-daemon                              synchingrepositories\n+git-archive                             mainporcelain\n+git-shortlog                            mainporcelain\n git-describe                            mainporcelain\n-git-diff                                mainporcelain           history\n-git-diff-files                          plumbinginterrogators\n-git-diff-index                          plumbinginterrogators\n-git-diff-tree                           plumbinginterrogators\n-git-difftool                            ancillaryinterrogators          complete\n+git-gc                                  mainporcelain\n+git-notes                               mainporcelain\n+git-worktree                            mainporcelain\n+git-bundle                              mainporcelain\n+git-range-diff                          mainporcelain\n+git-stage                                                               complete\n+git-reflog                              ancillarymanipulators           complete\n+git-remote                              ancillarymanipulators           complete\n+git-mergetool                           ancillarymanipulators           complete\n+git-filter-branch                       ancillarymanipulators\n+git-replace                             ancillarymanipulators           complete\n git-fast-export                         ancillarymanipulators\n git-fast-import                         ancillarymanipulators\n-git-fetch                               mainporcelain           remote\n-git-fetch-pack                          synchingrepositories\n-git-filter-branch                       ancillarymanipulators\n-git-fmt-merge-msg                       purehelpers\n-git-for-each-ref                        plumbinginterrogators\n-git-format-patch                        mainporcelain\n-git-fsck                                ancillaryinterrogators          complete\n-git-gc                                  mainporcelain\n-git-get-tar-commit-id                   plumbinginterrogators\n-git-grep                                mainporcelain           info\n-git-gui                                 mainporcelain\n-git-hash-object                         plumbingmanipulators\n-git-help                                ancillaryinterrogators          complete\n-git-http-backend                        synchingrepositories\n-git-http-fetch                          synchelpers\n-git-http-push                           synchelpers\n+git-pack-refs                           ancillarymanipulators\n+git-cvsimport                           foreignscminterface\n+git-cvsserver                           foreignscminterface\n+git-cvsexportcommit                     foreignscminterface\n+git-svn                                 foreignscminterface\n+git-p4                                  foreignscminterface\n+git-quiltimport                         foreignscminterface\n+git-archimport                          foreignscminterface\n git-imap-send                           foreignscminterface\n-git-index-pack                          plumbingmanipulators\n-git-init                                mainporcelain           init\n-git-instaweb                            ancillaryinterrogators          complete\n-git-interpret-trailers                  purehelpers\n-gitk                                    mainporcelain\n-git-log                                 mainporcelain           info\n-git-ls-files                            plumbinginterrogators\n-git-ls-remote                           plumbinginterrogators\n-git-ls-tree                             plumbinginterrogators\n-git-mailinfo                            purehelpers\n-git-mailsplit                           purehelpers\n-git-merge                               mainporcelain           history\n-git-merge-base                          plumbinginterrogators\n+git-apply                               plumbingmanipulators            complete\n git-merge-file                          plumbingmanipulators\n-git-merge-index                         plumbingmanipulators\n-git-merge-one-file                      purehelpers\n-git-mergetool                           ancillarymanipulators           complete\n-git-merge-tree                          ancillaryinterrogators\n-git-multi-pack-index                    plumbingmanipulators\n git-mktag                               plumbingmanipulators\n+git-hash-object                         plumbingmanipulators\n+git-update-ref                          plumbingmanipulators\n+git-symbolic-ref                        plumbingmanipulators\n+git-commit-tree                         plumbingmanipulators\n+git-commit-graph                        plumbingmanipulators\n git-mktree                              plumbingmanipulators\n-git-mv                                  mainporcelain           worktree\n-git-name-rev                            plumbinginterrogators\n-git-notes                               mainporcelain\n-git-p4                                  foreignscminterface\n git-pack-objects                        plumbingmanipulators\n-git-pack-redundant                      plumbinginterrogators\n-git-pack-refs                           ancillarymanipulators\n+git-unpack-objects                      plumbingmanipulators\n+git-index-pack                          plumbingmanipulators\n+git-multi-pack-index                    plumbingmanipulators\n+git-blame                               ancillaryinterrogators          complete\n+git-annotate                            ancillaryinterrogators\n+git-instaweb                            ancillaryinterrogators          complete\n+git-rerere                              ancillaryinterrogators\n+git-fsck                                ancillaryinterrogators          complete\n+git-whatchanged                         ancillaryinterrogators          complete\n+git-difftool                            ancillaryinterrogators          complete\n+git-merge-tree                          ancillaryinterrogators\n+git-count-objects                       ancillaryinterrogators\n+git-verify-commit                       ancillaryinterrogators\n+git-verify-tag                          ancillaryinterrogators\n+git-send-pack                           synchingrepositories\n+git-fetch-pack                          synchingrepositories\n git-parse-remote                        synchelpers\n-git-patch-id                            purehelpers\n-git-prune                               ancillarymanipulators\n-git-prune-packed                        plumbingmanipulators\n-git-pull                                mainporcelain           remote\n-git-push                                mainporcelain           remote\n-git-quiltimport                         foreignscminterface\n-git-range-diff                          mainporcelain\n-git-read-tree                           plumbingmanipulators\n-git-rebase                              mainporcelain           history\n git-receive-pack                        synchelpers\n-git-reflog                              ancillarymanipulators           complete\n-git-remote                              ancillarymanipulators           complete\n-git-repack                              ancillarymanipulators           complete\n-git-replace                             ancillarymanipulators           complete\n-git-request-pull                        foreignscminterface             complete\n-git-rerere                              ancillaryinterrogators\n-git-reset                               mainporcelain           worktree\n-git-revert                              mainporcelain\n+git-upload-pack                         synchelpers\n+git-upload-archive                      synchelpers\n+git-http-fetch                          synchelpers\n+git-http-push                           synchelpers\n+git-var                                 plumbinginterrogators\n git-rev-list                            plumbinginterrogators\n git-rev-parse                           plumbinginterrogators\n-git-rm                                  mainporcelain           worktree\n-git-send-email                          foreignscminterface             complete\n-git-send-pack                           synchingrepositories\n-git-shell                               synchelpers\n-git-shortlog                            mainporcelain\n-git-show                                mainporcelain           info\n-git-show-branch                         ancillaryinterrogators          complete\n-git-show-index                          plumbinginterrogators\n+git-for-each-ref                        plumbinginterrogators\n git-show-ref                            plumbinginterrogators\n-git-sh-i18n                             purehelpers\n+git-ls-remote                           plumbinginterrogators\n+git-diff-tree                           plumbinginterrogators\n+git-diff-index                          plumbinginterrogators\n+git-merge-base                          plumbinginterrogators\n+git-verify-pack                         plumbinginterrogators\n+git-pack-redundant                      plumbinginterrogators\n+git-unpack-file                         plumbinginterrogators\n+git-show-index                          plumbinginterrogators\n+git-get-tar-commit-id                   plumbinginterrogators\n+git-merge-one-file                      purehelpers\n git-sh-setup                            purehelpers\n-git-stash                               mainporcelain\n-git-stage                                                               complete\n-git-status                              mainporcelain           info\n+git-check-ref-format                    purehelpers\n+git-check-ignore                        purehelpers\n+git-check-attr                          purehelpers\n+git-credential                          purehelpers\n+git-credential-cache                    purehelpers\n+git-credential-store                    purehelpers\n+git-fmt-merge-msg                       purehelpers\n+git-check-mailmap                       purehelpers\n+git-mailsplit                           purehelpers\n+git-mailinfo                            purehelpers\n+git-interpret-trailers                  purehelpers\n+git-column                              purehelpers\n git-stripspace                          purehelpers\n-git-submodule                           mainporcelain\n-git-svn                                 foreignscminterface\n-git-symbolic-ref                        plumbingmanipulators\n-git-tag                                 mainporcelain           history\n-git-unpack-file                         plumbinginterrogators\n-git-unpack-objects                      plumbingmanipulators\n-git-update-index                        plumbingmanipulators\n-git-update-ref                          plumbingmanipulators\n-git-update-server-info                  synchingrepositories\n-git-upload-archive                      synchelpers\n-git-upload-pack                         synchelpers\n-git-var                                 plumbinginterrogators\n-git-verify-commit                       ancillaryinterrogators\n-git-verify-pack                         plumbinginterrogators\n-git-verify-tag                          ancillaryinterrogators\n-gitweb                                  ancillaryinterrogators\n-git-whatchanged                         ancillaryinterrogators          complete\n-git-worktree                            mainporcelain\n-git-write-tree                          plumbingmanipulators\n-gitattributes                           guide\n-gitcli                                  guide\n-gitcore-tutorial                        guide\n-gitcvs-migration                        guide\n-gitdiffcore                             guide\n-giteveryday                             guide\n-gitglossary                             guide\n-githooks                                guide\n-gitignore                               guide\n-gitmodules                              guide\n-gitnamespaces                           guide\n-gitrepository-layout                    guide\n-gitrevisions                            guide\n-gittutorial-2                           guide\n-gittutorial                             guide\n-gitworkflows                            guide\n+git-patch-id                            purehelpers\n+git-sh-i18n                             purehelpers\n-- \n2.20.1\n\n"},{"id":"369831","messageId":"20190221180522.vyoh6nxov4gupff6@ofb.net","threadId":"48834","inReplyTo":"20190219175413.18292-1-frederik@ofb.net","subject":"Re: [PATCH 0/1] de-alphabetize command list","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2019-02-21T18:05:22Z","receivedAt":"2019-02-21T18:05:29Z","isPatch":true,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"I realized that it would probably be easier to discuss this proposal\nif I attached the final command listing and the rendered manual page.\nPlease find them attached to this message.\n\nThank you,\n\nFrederick\n\nOn Tue, Feb 19, 2019 at 09:54:12AM -0800, Frederick Eaton wrote:\n>This is a follow-up to my proposal to de-alphabetize the command\n>listings in the git(1) manual page, from 6 July 2018.\n>\n>Some projects have manual page items listed in alphabetical order,\n>some don't. As I argued in my proposal, I find it easier to learn from\n>material which is not alphabetized. If this patch is accepted, I hope\n>that it will make the Git documentation more accessible to myself and\n>others.\n>\n>I produced the reordered command list in this patch using several\n>sources, as indicated by comments in the new command-list.txt file.\n>First, all the commands in the main part of \"gittutorial(7)\" appear in\n>order, then the commands in giteveryday(7). Then appear additional\n>commands from a friend's shell history, in reverse order of frequency.\n>Then gittutorial-2(7), then gitcore-tutorial(7). After that there is a\n>list of \"guides\", followed by about 100 commands not appearing in the\n>earlier lists. I kept the guides and the remaining commands in their\n>category groupings (guide, mainporcelain, ancillarymanipulators,\n>etc.), but ordered the commands within each category according to my\n>own judgment after skimming each manual page.\n>\n>To verify that the new list is a permutation of the most recent list,\n>I use the following command (it should produce no output and exit 0):\n>\n>    diff <(git show master:command-list.txt | grep -v '^#' | sort ) <(cat command-list.txt | grep -v '^#' | sort)\n>\n>Note this patch changes the order of commands appearing in the\n>generated file \"command-list.h\", which mostly seems to be used by\n>\"help.c\". Probably due to the various occurrences of QSORT in\n>\"help.c\", I think this reordering has no visible effect. I am willing\n>to do any additional testing which may be recommended to ensure that\n>this patch has no undesired consequences.\n>\n>Frederick Eaton (1):\n>  Prioritize list of commands appearing in git(1), via command-list.txt.\n>    Don't invoke 'sort' in Documentation/cmd-list.perl.\n>\n> Documentation/cmd-list.perl |   2 +-\n> command-list.txt            | 295 +++++++++++++++++++-----------------\n> 2 files changed, 158 insertions(+), 139 deletions(-)\n>\n>-- \n>2.20.1\n>\n\n\n# Command classification list\n# ---------------------------\n# All supported commands, builtin or external, must be described in\n# here. This info is used to list commands in various places. Each\n# command is on one line followed by one or more attributes.\n#\n# The first attribute group is mandatory and indicates the command\n# type. This group includes:\n#\n#   mainporcelain\n#   ancillarymanipulators\n#   ancillaryinterrogators\n#   foreignscminterface\n#   plumbingmanipulators\n#   plumbinginterrogators\n#   synchingrepositories\n#   synchelpers\n#   purehelpers\n#\n# The type names are self explanatory. But if you want to see what\n# command belongs to what group to get a better picture, have a look\n# at \"git\" man page, \"GIT COMMANDS\" section.\n#\n# Commands of type mainporcelain can also optionally have one of these\n# attributes:\n#\n#   init\n#   worktree\n#   info\n#   history\n#   remote\n#\n# These commands are considered \"common\" and will show up in \"git\n# help\" output in groups. Uncommon porcelain commands must not\n# specify any of these attributes.\n#\n# \"complete\" attribute is used to mark that the command should be\n# completable by git-completion.bash. Note that by default,\n# mainporcelain commands are completable so you don't need this\n# attribute.\n#\n# As part of the Git man page list, the man(5/7) guides are also\n# specified here, which can only have \"guide\" attribute and nothing\n# else.\n#\n# February 2019: This list had been sorted alphabetically but has been\n# reordered to make it easier for people to learn from the main git(1)\n# manual page. The new ordering is according to approximate usefulness\n# / frequency of use / order of use, with some grouping by topic. The\n# idea is to make it possible to read the manual page from beginning\n# to end and see the most important commands first, rather than\n# getting them in alphabetical order - in other words, to make the\n# manual page more like a table of contents and less like an index.\n# Please consider this when adding new commands.\n#\n### command list (do not change this line, also do not change alignment)\n# command name                          category [category] [category]\n# From gittutorial\ngit-help                                ancillaryinterrogators          complete\ngit-config                              ancillarymanipulators           complete\ngit-clone                               mainporcelain           init\ngit-init                                mainporcelain           init\ngit-add                                 mainporcelain           worktree\ngit-commit                              mainporcelain           history\ngit-diff                                mainporcelain           history\ngit-status                              mainporcelain           info\ngit-log                                 mainporcelain           info\ngit-branch                              mainporcelain           history\ngit-checkout                            mainporcelain           history\ngit-merge                               mainporcelain           history\ngitk                                    mainporcelain\ngit-pull                                mainporcelain           remote\ngit-fetch                               mainporcelain           remote\n# From tutorial NEXT STEPS\ngit-format-patch                        mainporcelain\ngit-bisect                              mainporcelain           info\ngiteveryday                             guide\ngitworkflows                            guide\ngitcvs-migration                        guide\n# From giteveryday\ngit-reset                               mainporcelain           worktree\ngit-rebase                              mainporcelain           history\ngit-tag                                 mainporcelain           history\ngit-push                                mainporcelain           remote\ngit-send-email                          foreignscminterface             complete\ngit-request-pull                        foreignscminterface             complete\ngit-am                                  mainporcelain\ngit-revert                              mainporcelain\ngit-daemon                              synchingrepositories\ngit-shell                               synchelpers\ngit-http-backend                        synchingrepositories\ngitweb                                  ancillaryinterrogators\n# From user feedback\ngit-grep                                mainporcelain           info\ngit-show                                mainporcelain           info\ngit-submodule                           mainporcelain\ngit-cherry-pick                         mainporcelain\ngit-clean                               mainporcelain\n# From gittutorial-2\ngit-cat-file                            plumbinginterrogators\ngit-ls-tree                             plumbinginterrogators\ngit-ls-files                            plumbinginterrogators\ngitcore-tutorial                        guide\ngitglossary                             guide\n# From gitcore-tutorial\ngit-update-index                        plumbingmanipulators\ngit-diff-files                          plumbinginterrogators\ngit-write-tree                          plumbingmanipulators\ngit-read-tree                           plumbingmanipulators\ngit-checkout-index                      plumbingmanipulators\ngit-show-branch                         ancillaryinterrogators          complete\ngit-name-rev                            plumbinginterrogators\ngit-merge-index                         plumbingmanipulators\ngit-repack                              ancillarymanipulators           complete\ngit-prune-packed                        plumbingmanipulators\ngit-update-server-info                  synchingrepositories\ngit-prune                               ancillarymanipulators\ngit-cherry                              plumbinginterrogators          complete\n# Guides, reordered\ngittutorial                             guide\ngittutorial-2                           guide\ngitrevisions                            guide\ngitignore                               guide\ngitcli                                  guide\ngitrepository-layout                    guide\ngitdiffcore                             guide\ngitmodules                              guide\ngithooks                                guide\ngitnamespaces                           guide\ngitattributes                           guide\n# All other commands, sorted by man page category and then by\n# approximate priority\ngit-stash                               mainporcelain\ngit-rm                                  mainporcelain           worktree\ngit-mv                                  mainporcelain           worktree\ngit-gui                                 mainporcelain\ngit-citool                              mainporcelain\ngit-archive                             mainporcelain\ngit-shortlog                            mainporcelain\ngit-describe                            mainporcelain\ngit-gc                                  mainporcelain\ngit-notes                               mainporcelain\ngit-worktree                            mainporcelain\ngit-bundle                              mainporcelain\ngit-range-diff                          mainporcelain\ngit-stage                                                               complete\ngit-reflog                              ancillarymanipulators           complete\ngit-remote                              ancillarymanipulators           complete\ngit-mergetool                           ancillarymanipulators           complete\ngit-filter-branch                       ancillarymanipulators\ngit-replace                             ancillarymanipulators           complete\ngit-fast-export                         ancillarymanipulators\ngit-fast-import                         ancillarymanipulators\ngit-pack-refs                           ancillarymanipulators\ngit-cvsimport                           foreignscminterface\ngit-cvsserver                           foreignscminterface\ngit-cvsexportcommit                     foreignscminterface\ngit-svn                                 foreignscminterface\ngit-p4                                  foreignscminterface\ngit-quiltimport                         foreignscminterface\ngit-archimport                          foreignscminterface\ngit-imap-send                           foreignscminterface\ngit-apply                               plumbingmanipulators            complete\ngit-merge-file                          plumbingmanipulators\ngit-mktag                               plumbingmanipulators\ngit-hash-object                         plumbingmanipulators\ngit-update-ref                          plumbingmanipulators\ngit-symbolic-ref                        plumbingmanipulators\ngit-commit-tree                         plumbingmanipulators\ngit-commit-graph                        plumbingmanipulators\ngit-mktree                              plumbingmanipulators\ngit-pack-objects                        plumbingmanipulators\ngit-unpack-objects                      plumbingmanipulators\ngit-index-pack                          plumbingmanipulators\ngit-multi-pack-index                    plumbingmanipulators\ngit-blame                               ancillaryinterrogators          complete\ngit-annotate                            ancillaryinterrogators\ngit-instaweb                            ancillaryinterrogators          complete\ngit-rerere                              ancillaryinterrogators\ngit-fsck                                ancillaryinterrogators          complete\ngit-whatchanged                         ancillaryinterrogators          complete\ngit-difftool                            ancillaryinterrogators          complete\ngit-merge-tree                          ancillaryinterrogators\ngit-count-objects                       ancillaryinterrogators\ngit-verify-commit                       ancillaryinterrogators\ngit-verify-tag                          ancillaryinterrogators\ngit-send-pack                           synchingrepositories\ngit-fetch-pack                          synchingrepositories\ngit-parse-remote                        synchelpers\ngit-receive-pack                        synchelpers\ngit-upload-pack                         synchelpers\ngit-upload-archive                      synchelpers\ngit-http-fetch                          synchelpers\ngit-http-push                           synchelpers\ngit-var                                 plumbinginterrogators\ngit-rev-list                            plumbinginterrogators\ngit-rev-parse                           plumbinginterrogators\ngit-for-each-ref                        plumbinginterrogators\ngit-show-ref                            plumbinginterrogators\ngit-ls-remote                           plumbinginterrogators\ngit-diff-tree                           plumbinginterrogators\ngit-diff-index                          plumbinginterrogators\ngit-merge-base                          plumbinginterrogators\ngit-verify-pack                         plumbinginterrogators\ngit-pack-redundant                      plumbinginterrogators\ngit-unpack-file                         plumbinginterrogators\ngit-show-index                          plumbinginterrogators\ngit-get-tar-commit-id                   plumbinginterrogators\ngit-merge-one-file                      purehelpers\ngit-sh-setup                            purehelpers\ngit-check-ref-format                    purehelpers\ngit-check-ignore                        purehelpers\ngit-check-attr                          purehelpers\ngit-credential                          purehelpers\ngit-credential-cache                    purehelpers\ngit-credential-store                    purehelpers\ngit-fmt-merge-msg                       purehelpers\ngit-check-mailmap                       purehelpers\ngit-mailsplit                           purehelpers\ngit-mailinfo                            purehelpers\ngit-interpret-trailers                  purehelpers\ngit-column                              purehelpers\ngit-stripspace                          purehelpers\ngit-patch-id                            purehelpers\ngit-sh-i18n                             purehelpers\n\n\nGIT(1)                            Git Manual                            GIT(1)\n\nNAME\n       git - the stupid content tracker\n\nSYNOPSIS\n       git [--version] [--help] [-C <path>] [-c <name>=<value>]\n           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\n           [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]\n           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\n           [--super-prefix=<path>]\n           <command> [<args>]\n\nDESCRIPTION\n       Git is a fast, scalable, distributed revision control system with an\n       unusually rich command set that provides both high-level operations and\n       full access to internals.\n\n       See gittutorial(7) to get started, then see giteveryday(7) for a useful\n       minimum set of commands. The Git User's Manual[1] has a more in-depth\n       introduction.\n\n       After you mastered the basic concepts, you can come back to this page\n       to learn what commands Git offers. You can learn more about individual\n       Git commands with \"git help command\". gitcli(7) manual page gives you\n       an overview of the command-line command syntax.\n\n       A formatted and hyperlinked copy of the latest Git documentation can be\n       viewed at https://git.github.io/htmldocs/git.html.\n\nOPTIONS\n       --version\n           Prints the Git suite version that the git program came from.\n\n       --help\n           Prints the synopsis and a list of the most commonly used commands.\n           If the option --all or -a is given then all available commands are\n           printed. If a Git command is named this option will bring up the\n           manual page for that command.\n\n           Other options are available to control how the manual page is\n           displayed. See git-help(1) for more information, because git --help\n           ...  is converted internally into git help ....\n\n       -C <path>\n           Run as if git was started in <path> instead of the current working\n           directory. When multiple -C options are given, each subsequent\n           non-absolute -C <path> is interpreted relative to the preceding -C\n           <path>.\n\n           This option affects options that expect path name like --git-dir\n           and --work-tree in that their interpretations of the path names\n           would be made relative to the working directory caused by the -C\n           option. For example the following invocations are equivalent:\n\n               git --git-dir=a.git --work-tree=b -C c status\n               git --git-dir=c/a.git --work-tree=c/b status\n\n       -c <name>=<value>\n           Pass a configuration parameter to the command. The value given will\n           override values from configuration files. The <name> is expected in\n           the same format as listed by git config (subkeys separated by\n           dots).\n\n           Note that omitting the = in git -c foo.bar ...  is allowed and sets\n           foo.bar to the boolean true value (just like [foo]bar would in a\n           config file). Including the equals but with an empty value (like\n           git -c foo.bar= ...) sets foo.bar to the empty string which git\n           config --type=bool will convert to false.\n\n       --exec-path[=<path>]\n           Path to wherever your core Git programs are installed. This can\n           also be controlled by setting the GIT_EXEC_PATH environment\n           variable. If no path is given, git will print the current setting\n           and then exit.\n\n       --html-path\n           Print the path, without trailing slash, where Git's HTML\n           documentation is installed and exit.\n\n       --man-path\n           Print the manpath (see man(1)) for the man pages for this version\n           of Git and exit.\n\n       --info-path\n           Print the path where the Info files documenting this version of Git\n           are installed and exit.\n\n       -p, --paginate\n           Pipe all output into less (or if set, $PAGER) if standard output is\n           a terminal. This overrides the pager.<cmd> configuration options\n           (see the \"Configuration Mechanism\" section below).\n\n       -P, --no-pager\n           Do not pipe Git output into a pager.\n\n       --git-dir=<path>\n           Set the path to the repository. This can also be controlled by\n           setting the GIT_DIR environment variable. It can be an absolute\n           path or relative path to current working directory.\n\n       --work-tree=<path>\n           Set the path to the working tree. It can be an absolute path or a\n           path relative to the current working directory. This can also be\n           controlled by setting the GIT_WORK_TREE environment variable and\n           the core.worktree configuration variable (see core.worktree in git-\n           config(1) for a more detailed discussion).\n\n       --namespace=<path>\n           Set the Git namespace. See gitnamespaces(7) for more details.\n           Equivalent to setting the GIT_NAMESPACE environment variable.\n\n       --super-prefix=<path>\n           Currently for internal use only. Set a prefix which gives a path\n           from above a repository down to its root. One use is to give\n           submodules context about the superproject that invoked it.\n\n       --bare\n           Treat the repository as a bare repository. If GIT_DIR environment\n           is not set, it is set to the current working directory.\n\n       --no-replace-objects\n           Do not use replacement refs to replace Git objects. See git-\n           replace(1) for more information.\n\n       --literal-pathspecs\n           Treat pathspecs literally (i.e. no globbing, no pathspec magic).\n           This is equivalent to setting the GIT_LITERAL_PATHSPECS environment\n           variable to 1.\n\n       --glob-pathspecs\n           Add \"glob\" magic to all pathspec. This is equivalent to setting the\n           GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on\n           individual pathspecs can be done using pathspec magic \":(literal)\"\n\n       --noglob-pathspecs\n           Add \"literal\" magic to all pathspec. This is equivalent to setting\n           the GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling\n           globbing on individual pathspecs can be done using pathspec magic\n           \":(glob)\"\n\n       --icase-pathspecs\n           Add \"icase\" magic to all pathspec. This is equivalent to setting\n           the GIT_ICASE_PATHSPECS environment variable to 1.\n\n       --no-optional-locks\n           Do not perform optional operations that require locks. This is\n           equivalent to setting the GIT_OPTIONAL_LOCKS to 0.\n\n       --list-cmds=group[,group...]\n           List commands by group. This is an internal/experimental option and\n           may change or be removed in the future. Supported groups are:\n           builtins, parseopt (builtin commands that use parse-options), main\n           (all commands in libexec directory), others (all other commands in\n           $PATH that have git- prefix), list-<category> (see categories in\n           command-list.txt), nohelpers (exclude helper commands), alias and\n           config (retrieve command list from config variable\n           completion.commands)\n\nGIT COMMANDS\n       We divide Git into high level (\"porcelain\") commands and low level\n       (\"plumbing\") commands.\n\nHIGH-LEVEL COMMANDS (PORCELAIN)\n       We separate the porcelain commands into the main commands and some\n       ancillary user utilities.\n\n   Main porcelain commands\n       git-clone(1)\n           Clone a repository into a new directory.\n\n       git-init(1)\n           Create an empty Git repository or reinitialize an existing one.\n\n       git-add(1)\n           Add file contents to the index.\n\n       git-commit(1)\n           Record changes to the repository.\n\n       git-diff(1)\n           Show changes between commits, commit and working tree, etc.\n\n       git-status(1)\n           Show the working tree status.\n\n       git-log(1)\n           Show commit logs.\n\n       git-branch(1)\n           List, create, or delete branches.\n\n       git-checkout(1)\n           Switch branches or restore working tree files.\n\n       git-merge(1)\n           Join two or more development histories together.\n\n       gitk(1)\n           The Git repository browser.\n\n       git-pull(1)\n           Fetch from and integrate with another repository or a local branch.\n\n       git-fetch(1)\n           Download objects and refs from another repository.\n\n       git-format-patch(1)\n           Prepare patches for e-mail submission.\n\n       git-bisect(1)\n           Use binary search to find the commit that introduced a bug.\n\n       git-reset(1)\n           Reset current HEAD to the specified state.\n\n       git-rebase(1)\n           Reapply commits on top of another base tip.\n\n       git-tag(1)\n           Create, list, delete or verify a tag object signed with GPG.\n\n       git-push(1)\n           Update remote refs along with associated objects.\n\n       git-am(1)\n           Apply a series of patches from a mailbox.\n\n       git-revert(1)\n           Revert some existing commits.\n\n       git-grep(1)\n           Print lines matching a pattern.\n\n       git-show(1)\n           Show various types of objects.\n\n       git-submodule(1)\n           Initialize, update or inspect submodules.\n\n       git-cherry-pick(1)\n           Apply the changes introduced by some existing commits.\n\n       git-clean(1)\n           Remove untracked files from the working tree.\n\n       git-stash(1)\n           Stash the changes in a dirty working directory away.\n\n       git-rm(1)\n           Remove files from the working tree and from the index.\n\n       git-mv(1)\n           Move or rename a file, a directory, or a symlink.\n\n       git-gui(1)\n           A portable graphical interface to Git.\n\n       git-citool(1)\n           Graphical alternative to git-commit.\n\n       git-archive(1)\n           Create an archive of files from a named tree.\n\n       git-shortlog(1)\n           Summarize git log output.\n\n       git-describe(1)\n           Give an object a human readable name based on an available ref.\n\n       git-gc(1)\n           Cleanup unnecessary files and optimize the local repository.\n\n       git-notes(1)\n           Add or inspect object notes.\n\n       git-worktree(1)\n           Manage multiple working trees.\n\n       git-bundle(1)\n           Move objects and refs by archive.\n\n       git-range-diff(1)\n           Compare two commit ranges (e.g. two versions of a branch).\n\n   Ancillary Commands\n       Manipulators:\n\n       git-config(1)\n           Get and set repository or global options.\n\n       git-repack(1)\n           Pack unpacked objects in a repository.\n\n       git-prune(1)\n           Prune all unreachable objects from the object database.\n\n       git-reflog(1)\n           Manage reflog information.\n\n       git-remote(1)\n           Manage set of tracked repositories.\n\n       git-mergetool(1)\n           Run merge conflict resolution tools to resolve merge conflicts.\n\n       git-filter-branch(1)\n           Rewrite branches.\n\n       git-replace(1)\n           Create, list, delete refs to replace objects.\n\n       git-fast-export(1)\n           Git data exporter.\n\n       git-fast-import(1)\n           Backend for fast Git data importers.\n\n       git-pack-refs(1)\n           Pack heads and tags for efficient repository access.\n\n       Interrogators:\n\n       git-help(1)\n           Display help information about Git.\n\n       gitweb(1)\n           Git web interface (web frontend to Git repositories).\n\n       git-show-branch(1)\n           Show branches and their commits.\n\n       git-blame(1)\n           Show what revision and author last modified each line of a file.\n\n       git-annotate(1)\n           Annotate file lines with commit information.\n\n       git-instaweb(1)\n           Instantly browse your working repository in gitweb.\n\n       git-rerere(1)\n           Reuse recorded resolution of conflicted merges.\n\n       git-fsck(1)\n           Verifies the connectivity and validity of the objects in the\n           database.\n\n       git-whatchanged(1)\n           Show logs with difference each commit introduces.\n\n       git-difftool(1)\n           Show changes using common diff tools.\n\n       git-merge-tree(1)\n           Show three-way merge without touching index.\n\n       git-count-objects(1)\n           Count unpacked number of objects and their disk consumption.\n\n       git-verify-commit(1)\n           Check the GPG signature of commits.\n\n       git-verify-tag(1)\n           Check the GPG signature of tags.\n\n   Interacting with Others\n       These commands are to interact with foreign SCM and with other people\n       via patch over e-mail.\n\n       git-send-email(1)\n           Send a collection of patches as emails.\n\n       git-request-pull(1)\n           Generates a summary of pending changes.\n\n       git-cvsimport(1)\n           Salvage your data out of another SCM people love to hate.\n\n       git-cvsserver(1)\n           A CVS server emulator for Git.\n\n       git-cvsexportcommit(1)\n           Export a single commit to a CVS checkout.\n\n       git-svn(1)\n           Bidirectional operation between a Subversion repository and Git.\n\n       git-p4(1)\n           Import from and submit to Perforce repositories.\n\n       git-quiltimport(1)\n           Applies a quilt patchset onto the current branch.\n\n       git-archimport(1)\n           Import a GNU Arch repository into Git.\n\n       git-imap-send(1)\n           Send a collection of patches from stdin to an IMAP folder.\n\nLOW-LEVEL COMMANDS (PLUMBING)\n       Although Git includes its own porcelain layer, its low-level commands\n       are sufficient to support development of alternative porcelains.\n       Developers of such porcelains might start by reading about git-update-\n       index(1) and git-read-tree(1).\n\n       The interface (input, output, set of options and the semantics) to\n       these low-level commands are meant to be a lot more stable than\n       Porcelain level commands, because these commands are primarily for\n       scripted use. The interface to Porcelain commands on the other hand are\n       subject to change in order to improve the end user experience.\n\n       The following description divides the low-level commands into commands\n       that manipulate objects (in the repository, index, and working tree),\n       commands that interrogate and compare objects, and commands that move\n       objects and references between repositories.\n\n   Manipulation commands\n       git-update-index(1)\n           Register file contents in the working tree to the index.\n\n       git-write-tree(1)\n           Create a tree object from the current index.\n\n       git-read-tree(1)\n           Reads tree information into the index.\n\n       git-checkout-index(1)\n           Copy files from the index to the working tree.\n\n       git-merge-index(1)\n           Run a merge for files needing merging.\n\n       git-prune-packed(1)\n           Remove extra objects that are already in pack files.\n\n       git-apply(1)\n           Apply a patch to files and/or to the index.\n\n       git-merge-file(1)\n           Run a three-way file merge.\n\n       git-mktag(1)\n           Creates a tag object.\n\n       git-hash-object(1)\n           Compute object ID and optionally creates a blob from a file.\n\n       git-update-ref(1)\n           Update the object name stored in a ref safely.\n\n       git-symbolic-ref(1)\n           Read, modify and delete symbolic refs.\n\n       git-commit-tree(1)\n           Create a new commit object.\n\n       git-commit-graph(1)\n           Write and verify Git commit-graph files.\n\n       git-mktree(1)\n           Build a tree-object from ls-tree formatted text.\n\n       git-pack-objects(1)\n           Create a packed archive of objects.\n\n       git-unpack-objects(1)\n           Unpack objects from a packed archive.\n\n       git-index-pack(1)\n           Build pack index file for an existing packed archive.\n\n       git-multi-pack-index(1)\n           Write and verify multi-pack-indexes.\n\n   Interrogation commands\n       git-cat-file(1)\n           Provide content or type and size information for repository\n           objects.\n\n       git-ls-tree(1)\n           List the contents of a tree object.\n\n       git-ls-files(1)\n           Show information about files in the index and the working tree.\n\n       git-diff-files(1)\n           Compares files in the working tree and the index.\n\n       git-name-rev(1)\n           Find symbolic names for given revs.\n\n       git-cherry(1)\n           Find commits yet to be applied to upstream.\n\n       git-var(1)\n           Show a Git logical variable.\n\n       git-rev-list(1)\n           Lists commit objects in reverse chronological order.\n\n       git-rev-parse(1)\n           Pick out and massage parameters.\n\n       git-for-each-ref(1)\n           Output information on each ref.\n\n       git-show-ref(1)\n           List references in a local repository.\n\n       git-ls-remote(1)\n           List references in a remote repository.\n\n       git-diff-tree(1)\n           Compares the content and mode of blobs found via two tree objects.\n\n       git-diff-index(1)\n           Compare a tree to the working tree or index.\n\n       git-merge-base(1)\n           Find as good common ancestors as possible for a merge.\n\n       git-verify-pack(1)\n           Validate packed Git archive files.\n\n       git-pack-redundant(1)\n           Find redundant pack files.\n\n       git-unpack-file(1)\n           Creates a temporary file with a blob's contents.\n\n       git-show-index(1)\n           Show packed archive index.\n\n       git-get-tar-commit-id(1)\n           Extract commit ID from an archive created using git-archive.\n\n       In general, the interrogate commands do not touch the files in the\n       working tree.\n\n   Synching repositories\n       git-daemon(1)\n           A really simple server for Git repositories.\n\n       git-http-backend(1)\n           Server side implementation of Git over HTTP.\n\n       git-update-server-info(1)\n           Update auxiliary info file to help dumb servers.\n\n       git-send-pack(1)\n           Push objects over Git protocol to another repository.\n\n       git-fetch-pack(1)\n           Receive missing objects from another repository.\n\n       The following are helper commands used by the above; end users\n       typically do not use them directly.\n\n       git-shell(1)\n           Restricted login shell for Git-only SSH access.\n\n       git-parse-remote(1)\n           Routines to help parsing remote repository access parameters.\n\n       git-receive-pack(1)\n           Receive what is pushed into the repository.\n\n       git-upload-pack(1)\n           Send objects packed back to git-fetch-pack.\n\n       git-upload-archive(1)\n           Send archive back to git-archive.\n\n       git-http-fetch(1)\n           Download from a remote Git repository via HTTP.\n\n       git-http-push(1)\n           Push objects over HTTP/DAV to another repository.\n\n   Internal helper commands\n       These are internal helper commands used by other commands; end users\n       typically do not use them directly.\n\n       git-merge-one-file(1)\n           The standard helper program to use with git-merge-index.\n\n       git-sh-setup(1)\n           Common Git shell script setup code.\n\n       git-check-ref-format(1)\n           Ensures that a reference name is well formed.\n\n       git-check-ignore(1)\n           Debug gitignore / exclude files.\n\n       git-check-attr(1)\n           Display gitattributes information.\n\n       git-credential(1)\n           Retrieve and store user credentials.\n\n       git-credential-cache(1)\n           Helper to temporarily store passwords in memory.\n\n       git-credential-store(1)\n           Helper to store credentials on disk.\n\n       git-fmt-merge-msg(1)\n           Produce a merge commit message.\n\n       git-check-mailmap(1)\n           Show canonical names and email addresses of contacts.\n\n       git-mailsplit(1)\n           Simple UNIX mbox splitter program.\n\n       git-mailinfo(1)\n           Extracts patch and authorship from a single e-mail message.\n\n       git-interpret-trailers(1)\n           add or parse structured information in commit messages.\n\n       git-column(1)\n           Display data in columns.\n\n       git-stripspace(1)\n           Remove unnecessary whitespace.\n\n       git-patch-id(1)\n           Compute unique ID for a patch.\n\n       git-sh-i18n(1)\n           Git's i18n setup code for shell scripts.\n\nCONFIGURATION MECHANISM\n       Git uses a simple text format to store customizations that are per\n       repository and are per user. Such a configuration file may look like\n       this:\n\n           #\n           # A '#' or ';' character indicates a comment.\n           #\n\n           ; core variables\n           [core]\n                   ; Don't trust file modes\n                   filemode = false\n\n           ; user identity\n           [user]\n                   name = \"Junio C Hamano\"\n                   email = \"gitster@pobox.com\"\n\n       Various commands read from the configuration file and adjust their\n       operation accordingly. See git-config(1) for a list and more details\n       about the configuration mechanism.\n\nIDENTIFIER TERMINOLOGY\n       <object>\n           Indicates the object name for any type of object.\n\n       <blob>\n           Indicates a blob object name.\n\n       <tree>\n           Indicates a tree object name.\n\n       <commit>\n           Indicates a commit object name.\n\n       <tree-ish>\n           Indicates a tree, commit or tag object name. A command that takes a\n           <tree-ish> argument ultimately wants to operate on a <tree> object\n           but automatically dereferences <commit> and <tag> objects that\n           point at a <tree>.\n\n       <commit-ish>\n           Indicates a commit or tag object name. A command that takes a\n           <commit-ish> argument ultimately wants to operate on a <commit>\n           object but automatically dereferences <tag> objects that point at a\n           <commit>.\n\n       <type>\n           Indicates that an object type is required. Currently one of: blob,\n           tree, commit, or tag.\n\n       <file>\n           Indicates a filename - almost always relative to the root of the\n           tree structure GIT_INDEX_FILE describes.\n\nSYMBOLIC IDENTIFIERS\n       Any Git command accepting any <object> can also use the following\n       symbolic notation:\n\n       HEAD\n           indicates the head of the current branch.\n\n       <tag>\n           a valid tag name (i.e. a refs/tags/<tag> reference).\n\n       <head>\n           a valid head name (i.e. a refs/heads/<head> reference).\n\n       For a more complete list of ways to spell object names, see \"SPECIFYING\n       REVISIONS\" section in gitrevisions(7).\n\nFILE/DIRECTORY STRUCTURE\n       Please see the gitrepository-layout(5) document.\n\n       Read githooks(5) for more details about each hook.\n\n       Higher level SCMs may provide and manage additional information in the\n       $GIT_DIR.\n\nTERMINOLOGY\n       Please see gitglossary(7).\n\nENVIRONMENT VARIABLES\n       Various Git commands use the following environment variables:\n\n   The Git Repository\n       These environment variables apply to all core Git commands. Nb: it is\n       worth noting that they may be used/overridden by SCMS sitting above Git\n       so take care if using a foreign front-end.\n\n       GIT_INDEX_FILE\n           This environment allows the specification of an alternate index\n           file. If not specified, the default of $GIT_DIR/index is used.\n\n       GIT_INDEX_VERSION\n           This environment variable allows the specification of an index\n           version for new repositories. It won't affect existing index files.\n           By default index file version 2 or 3 is used. See git-update-\n           index(1) for more information.\n\n       GIT_OBJECT_DIRECTORY\n           If the object storage directory is specified via this environment\n           variable then the sha1 directories are created underneath -\n           otherwise the default $GIT_DIR/objects directory is used.\n\n       GIT_ALTERNATE_OBJECT_DIRECTORIES\n           Due to the immutable nature of Git objects, old objects can be\n           archived into shared, read-only directories. This variable\n           specifies a \":\" separated (on Windows \";\" separated) list of Git\n           object directories which can be used to search for Git objects. New\n           objects will not be written to these directories.\n\n           Entries that begin with \" (double-quote) will be interpreted as\n           C-style quoted paths, removing leading and trailing double-quotes\n           and respecting backslash escapes. E.g., the value\n           \"path-with-\\\"-and-:-in-it\":vanilla-path has two paths:\n           path-with-\"-and-:-in-it and vanilla-path.\n\n       GIT_DIR\n           If the GIT_DIR environment variable is set then it specifies a path\n           to use instead of the default .git for the base of the repository.\n           The --git-dir command-line option also sets this value.\n\n       GIT_WORK_TREE\n           Set the path to the root of the working tree. This can also be\n           controlled by the --work-tree command-line option and the\n           core.worktree configuration variable.\n\n       GIT_NAMESPACE\n           Set the Git namespace; see gitnamespaces(7) for details. The\n           --namespace command-line option also sets this value.\n\n       GIT_CEILING_DIRECTORIES\n           This should be a colon-separated list of absolute paths. If set, it\n           is a list of directories that Git should not chdir up into while\n           looking for a repository directory (useful for excluding\n           slow-loading network directories). It will not exclude the current\n           working directory or a GIT_DIR set on the command line or in the\n           environment. Normally, Git has to read the entries in this list and\n           resolve any symlink that might be present in order to compare them\n           with the current directory. However, if even this access is slow,\n           you can add an empty entry to the list to tell Git that the\n           subsequent entries are not symlinks and needn't be resolved; e.g.,\n           GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink.\n\n       GIT_DISCOVERY_ACROSS_FILESYSTEM\n           When run in a directory that does not have \".git\" repository\n           directory, Git tries to find such a directory in the parent\n           directories to find the top of the working tree, but by default it\n           does not cross filesystem boundaries. This environment variable can\n           be set to true to tell Git not to stop at filesystem boundaries.\n           Like GIT_CEILING_DIRECTORIES, this will not affect an explicit\n           repository directory set via GIT_DIR or on the command line.\n\n       GIT_COMMON_DIR\n           If this variable is set to a path, non-worktree files that are\n           normally in $GIT_DIR will be taken from this path instead.\n           Worktree-specific files such as HEAD or index are taken from\n           $GIT_DIR. See gitrepository-layout(5) and git-worktree(1) for\n           details. This variable has lower precedence than other path\n           variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...\n\n   Git Commits\n       GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME,\n       GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, EMAIL\n           see git-commit-tree(1)\n\n   Git Diffs\n       GIT_DIFF_OPTS\n           Only valid setting is \"--unified=??\" or \"-u??\" to set the number of\n           context lines shown when a unified diff is created. This takes\n           precedence over any \"-U\" or \"--unified\" option value passed on the\n           Git diff command line.\n\n       GIT_EXTERNAL_DIFF\n           When the environment variable GIT_EXTERNAL_DIFF is set, the program\n           named by it is called, instead of the diff invocation described\n           above. For a path that is added, removed, or modified,\n           GIT_EXTERNAL_DIFF is called with 7 parameters:\n\n               path old-file old-hex old-mode new-file new-hex new-mode\n\n           where:\n\n       <old|new>-file\n           are files GIT_EXTERNAL_DIFF can use to read the contents of\n           <old|new>,\n\n       <old|new>-hex\n           are the 40-hexdigit SHA-1 hashes,\n\n       <old|new>-mode\n           are the octal representation of the file modes.\n\n           The file parameters can point at the user's working file (e.g.\n           new-file in \"git-diff-files\"), /dev/null (e.g.  old-file when a new\n           file is added), or a temporary file (e.g.  old-file in the index).\n           GIT_EXTERNAL_DIFF should not worry about unlinking the temporary\n           file --- it is removed when GIT_EXTERNAL_DIFF exits.\n\n           For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1\n           parameter, <path>.\n\n           For each path GIT_EXTERNAL_DIFF is called, two environment\n           variables, GIT_DIFF_PATH_COUNTER and GIT_DIFF_PATH_TOTAL are set.\n\n       GIT_DIFF_PATH_COUNTER\n           A 1-based counter incremented by one for every path.\n\n       GIT_DIFF_PATH_TOTAL\n           The total number of paths.\n\n   other\n       GIT_MERGE_VERBOSITY\n           A number controlling the amount of output shown by the recursive\n           merge strategy. Overrides merge.verbosity. See git-merge(1)\n\n       GIT_PAGER\n           This environment variable overrides $PAGER. If it is set to an\n           empty string or to the value \"cat\", Git will not launch a pager.\n           See also the core.pager option in git-config(1).\n\n       GIT_EDITOR\n           This environment variable overrides $EDITOR and $VISUAL. It is used\n           by several Git commands when, on interactive mode, an editor is to\n           be launched. See also git-var(1) and the core.editor option in git-\n           config(1).\n\n       GIT_SSH, GIT_SSH_COMMAND\n           If either of these environment variables is set then git fetch and\n           git push will use the specified command instead of ssh when they\n           need to connect to a remote system. The command-line parameters\n           passed to the configured command are determined by the ssh variant.\n           See ssh.variant option in git-config(1) for details.\n\n       + $GIT_SSH_COMMAND takes precedence over $GIT_SSH, and is interpreted\n       by the shell, which allows additional arguments to be included.\n       $GIT_SSH on the other hand must be just the path to a program (which\n       can be a wrapper shell script, if additional arguments are needed).\n\n       + Usually it is easier to configure any desired options through your\n       personal .ssh/config file. Please consult your ssh documentation for\n       further details.\n\n       GIT_SSH_VARIANT\n           If this environment variable is set, it overrides Git's\n           autodetection whether GIT_SSH/GIT_SSH_COMMAND/core.sshCommand refer\n           to OpenSSH, plink or tortoiseplink. This variable overrides the\n           config setting ssh.variant that serves the same purpose.\n\n       GIT_ASKPASS\n           If this environment variable is set, then Git commands which need\n           to acquire passwords or passphrases (e.g. for HTTP or IMAP\n           authentication) will call this program with a suitable prompt as\n           command-line argument and read the password from its STDOUT. See\n           also the core.askPass option in git-config(1).\n\n       GIT_TERMINAL_PROMPT\n           If this environment variable is set to 0, git will not prompt on\n           the terminal (e.g., when asking for HTTP authentication).\n\n       GIT_CONFIG_NOSYSTEM\n           Whether to skip reading settings from the system-wide\n           $(prefix)/etc/gitconfig file. This environment variable can be used\n           along with $HOME and $XDG_CONFIG_HOME to create a predictable\n           environment for a picky script, or you can set it temporarily to\n           avoid using a buggy /etc/gitconfig file while waiting for someone\n           with sufficient permissions to fix it.\n\n       GIT_FLUSH\n           If this environment variable is set to \"1\", then commands such as\n           git blame (in incremental mode), git rev-list, git log, git\n           check-attr and git check-ignore will force a flush of the output\n           stream after each record have been flushed. If this variable is set\n           to \"0\", the output of these commands will be done using completely\n           buffered I/O. If this environment variable is not set, Git will\n           choose buffered or record-oriented flushing based on whether stdout\n           appears to be redirected to a file or not.\n\n       GIT_TRACE\n           Enables general trace messages, e.g. alias expansion, built-in\n           command execution and external command execution.\n\n           If this variable is set to \"1\", \"2\" or \"true\" (comparison is case\n           insensitive), trace messages will be printed to stderr.\n\n           If the variable is set to an integer value greater than 2 and lower\n           than 10 (strictly) then Git will interpret this value as an open\n           file descriptor and will try to write the trace messages into this\n           file descriptor.\n\n           Alternatively, if the variable is set to an absolute path (starting\n           with a / character), Git will interpret this as a file path and\n           will try to append the trace messages to it.\n\n           Unsetting the variable, or setting it to empty, \"0\" or \"false\"\n           (case insensitive) disables trace messages.\n\n       GIT_TRACE_FSMONITOR\n           Enables trace messages for the filesystem monitor extension. See\n           GIT_TRACE for available trace output options.\n\n       GIT_TRACE_PACK_ACCESS\n           Enables trace messages for all accesses to any packs. For each\n           access, the pack file name and an offset in the pack is recorded.\n           This may be helpful for troubleshooting some pack-related\n           performance problems. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_PACKET\n           Enables trace messages for all packets coming in or out of a given\n           program. This can help with debugging object negotiation or other\n           protocol issues. Tracing is turned off at a packet starting with\n           \"PACK\" (but see GIT_TRACE_PACKFILE below). See GIT_TRACE for\n           available trace output options.\n\n       GIT_TRACE_PACKFILE\n           Enables tracing of packfiles sent or received by a given program.\n           Unlike other trace output, this trace is verbatim: no headers, and\n           no quoting of binary data. You almost certainly want to direct into\n           a file (e.g., GIT_TRACE_PACKFILE=/tmp/my.pack) rather than\n           displaying it on the terminal or mixing it with other trace output.\n\n           Note that this is currently only implemented for the client side of\n           clones and fetches.\n\n       GIT_TRACE_PERFORMANCE\n           Enables performance related trace messages, e.g. total execution\n           time of each Git command. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_SETUP\n           Enables trace messages printing the .git, working tree and current\n           working directory after Git has completed its setup phase. See\n           GIT_TRACE for available trace output options.\n\n       GIT_TRACE_SHALLOW\n           Enables trace messages that can help debugging fetching / cloning\n           of shallow repositories. See GIT_TRACE for available trace output\n           options.\n\n       GIT_TRACE_CURL\n           Enables a curl full trace dump of all incoming and outgoing data,\n           including descriptive information, of the git transport protocol.\n           This is similar to doing curl --trace-ascii on the command line.\n           This option overrides setting the GIT_CURL_VERBOSE environment\n           variable. See GIT_TRACE for available trace output options.\n\n       GIT_TRACE_CURL_NO_DATA\n           When a curl trace is enabled (see GIT_TRACE_CURL above), do not\n           dump data (that is, only dump info lines and headers).\n\n       GIT_REDACT_COOKIES\n           This can be set to a comma-separated list of strings. When a curl\n           trace is enabled (see GIT_TRACE_CURL above), whenever a \"Cookies:\"\n           header sent by the client is dumped, values of cookies whose key is\n           in that list (case-sensitive) are redacted.\n\n       GIT_LITERAL_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs\n           literally, rather than as glob patterns. For example, running\n           GIT_LITERAL_PATHSPECS=1 git log -- '*.c' will search for commits\n           that touch the path *.c, not any paths that the glob *.c matches.\n           You might want this if you are feeding literal paths to Git (e.g.,\n           paths previously given to you by git ls-tree, --raw diff output,\n           etc).\n\n       GIT_GLOB_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           glob patterns (aka \"glob\" magic).\n\n       GIT_NOGLOB_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           literal (aka \"literal\" magic).\n\n       GIT_ICASE_PATHSPECS\n           Setting this variable to 1 will cause Git to treat all pathspecs as\n           case-insensitive.\n\n       GIT_REFLOG_ACTION\n           When a ref is updated, reflog entries are created to keep track of\n           the reason why the ref was updated (which is typically the name of\n           the high-level command that updated the ref), in addition to the\n           old and new values of the ref. A scripted Porcelain command can use\n           set_reflog_action helper function in git-sh-setup to set its name\n           to this variable when it is invoked as the top level command by the\n           end user, to be recorded in the body of the reflog.\n\n       GIT_REF_PARANOIA\n           If set to 1, include broken or badly named refs when iterating over\n           lists of refs. In a normal, non-corrupted repository, this does\n           nothing. However, enabling it may help git to detect and abort some\n           operations in the presence of broken refs. Git sets this variable\n           automatically when performing destructive operations like git-\n           prune(1). You should not need to set it yourself unless you want to\n           be paranoid about making sure an operation has touched every ref\n           (e.g., because you are cloning a repository to make a backup).\n\n       GIT_ALLOW_PROTOCOL\n           If set to a colon-separated list of protocols, behave as if\n           protocol.allow is set to never, and each of the listed protocols\n           has protocol.<name>.allow set to always (overriding any existing\n           configuration). In other words, any protocol not mentioned will be\n           disallowed (i.e., this is a whitelist, not a blacklist). See the\n           description of protocol.allow in git-config(1) for more details.\n\n       GIT_PROTOCOL_FROM_USER\n           Set to 0 to prevent protocols used by fetch/push/clone which are\n           configured to the user state. This is useful to restrict recursive\n           submodule initialization from an untrusted repository or for\n           programs which feed potentially-untrusted URLS to git commands. See\n           git-config(1) for more details.\n\n       GIT_PROTOCOL\n           For internal use only. Used in handshaking the wire protocol.\n           Contains a colon : separated list of keys with optional values\n           key[=value]. Presence of unknown keys and values must be ignored.\n\n       GIT_OPTIONAL_LOCKS\n           If set to 0, Git will complete any requested operation without\n           performing any optional sub-operations that require taking a lock.\n           For example, this will prevent git status from refreshing the index\n           as a side effect. This is useful for processes running in the\n           background which do not want to cause lock contention with other\n           operations on the repository. Defaults to 1.\n\n       GIT_REDIRECT_STDIN, GIT_REDIRECT_STDOUT, GIT_REDIRECT_STDERR\n           Windows-only: allow redirecting the standard input/output/error\n           handles to paths specified by the environment variables. This is\n           particularly useful in multi-threaded applications where the\n           canonical way to pass standard handles via CreateProcess() is not\n           an option because it would require the handles to be marked\n           inheritable (and consequently every spawned process would inherit\n           them, possibly blocking regular Git operations). The primary\n           intended use case is to use named pipes for communication (e.g.\n           \\\\.\\pipe\\my-git-stdin-123).\n\n           Two special values are supported: off will simply close the\n           corresponding standard handle, and if GIT_REDIRECT_STDERR is 2>&1,\n           standard error will be redirected to the same handle as standard\n           output.\n\n       GIT_PRINT_SHA1_ELLIPSIS (deprecated)\n           If set to yes, print an ellipsis following an (abbreviated) SHA-1\n           value. This affects indications of detached HEADs (git-checkout(1))\n           and the raw diff output (git-diff(1)). Printing an ellipsis in the\n           cases mentioned is no longer considered adequate and support for it\n           is likely to be removed in the foreseeable future (along with the\n           variable).\n\nDISCUSSION\n       More detail on the following is available from the Git concepts chapter\n       of the user-manual[2] and gitcore-tutorial(7).\n\n       A Git project normally consists of a working directory with a \".git\"\n       subdirectory at the top level. The .git directory contains, among other\n       things, a compressed object database representing the complete history\n       of the project, an \"index\" file which links that history to the current\n       contents of the working tree, and named pointers into that history such\n       as tags and branch heads.\n\n       The object database contains objects of three main types: blobs, which\n       hold file data; trees, which point to blobs and other trees to build up\n       directory hierarchies; and commits, which each reference a single tree\n       and some number of parent commits.\n\n       The commit, equivalent to what other systems call a \"changeset\" or\n       \"version\", represents a step in the project's history, and each parent\n       represents an immediately preceding step. Commits with more than one\n       parent represent merges of independent lines of development.\n\n       All objects are named by the SHA-1 hash of their contents, normally\n       written as a string of 40 hex digits. Such names are globally unique.\n       The entire history leading up to a commit can be vouched for by signing\n       just that commit. A fourth object type, the tag, is provided for this\n       purpose.\n\n       When first created, objects are stored in individual files, but for\n       efficiency may later be compressed together into \"pack files\".\n\n       Named pointers called refs mark interesting points in history. A ref\n       may contain the SHA-1 name of an object or the name of another ref.\n       Refs with names beginning ref/head/ contain the SHA-1 name of the most\n       recent commit (or \"head\") of a branch under development. SHA-1 names of\n       tags of interest are stored under ref/tags/. A special ref named HEAD\n       contains the name of the currently checked-out branch.\n\n       The index file is initialized with a list of all paths and, for each\n       path, a blob object and a set of attributes. The blob object represents\n       the contents of the file as of the head of the current branch. The\n       attributes (last modified time, size, etc.) are taken from the\n       corresponding file in the working tree. Subsequent changes to the\n       working tree can be found by comparing these attributes. The index may\n       be updated with new content, and new commits may be created from the\n       content stored in the index.\n\n       The index is also capable of storing multiple entries (called \"stages\")\n       for a given pathname. These stages are used to hold the various\n       unmerged version of a file when a merge is in progress.\n\nFURTHER DOCUMENTATION\n       See the references in the \"description\" section to get started using\n       Git. The following is probably more detail than necessary for a\n       first-time user.\n\n       The Git concepts chapter of the user-manual[2] and gitcore-tutorial(7)\n       both provide introductions to the underlying Git architecture.\n\n       See gitworkflows(7) for an overview of recommended workflows.\n\n       See also the howto[3] documents for some useful examples.\n\n       The internals are documented in the Git API documentation[4].\n\n       Users migrating from CVS may also want to read gitcvs-migration(7).\n\nAUTHORS\n       Git was started by Linus Torvalds, and is currently maintained by Junio\n       C Hamano. Numerous contributions have come from the Git mailing list\n       <git@vger.kernel.org[5]>.\n       http://www.openhub.net/p/git/contributors/summary gives you a more\n       complete list of contributors.\n\n       If you have a clone of git.git itself, the output of git-shortlog(1)\n       and git-blame(1) can show you the authors for specific parts of the\n       project.\n\nREPORTING BUGS\n       Report bugs to the Git mailing list <git@vger.kernel.org[5]> where the\n       development and maintenance is primarily done. You do not have to be\n       subscribed to the list to send a message there. See the list archive at\n       https://public-inbox.org/git for previous bug reports and other\n       discussions.\n\n       Issues which are security relevant should be disclosed privately to the\n       Git Security mailing list <git-security@googlegroups.com[6]>.\n\nSEE ALSO\n       gittutorial(7), gittutorial-2(7), giteveryday(7), gitcvs-migration(7),\n       gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User's\n       Manual[1], gitworkflows(7)\n\nGIT\n       Part of the git(1) suite\n\nNOTES\n        1. Git User's Manual\n           file:///home/frederik/share/doc/git-doc/user-manual.html\n\n        2. Git concepts chapter of the user-manual\n           file:///home/frederik/share/doc/git-doc/user-manual.html#git-concepts\n\n        3. howto\n           file:///home/frederik/share/doc/git-doc/howto-index.html\n\n        4. Git API documentation\n           file:///home/frederik/share/doc/git-doc/technical/api-index.html\n\n        5. git@vger.kernel.org\n           mailto:git@vger.kernel.org\n\n        6. git-security@googlegroups.com\n           mailto:git-security@googlegroups.com\n\nGit 2.21.0.rc1.9.g3f              02/18/2019                            GIT(1)\n"},{"id":"371127","messageId":"20190311090436.brdk7un7dto7rrhh@localhost","threadId":"48834","inReplyTo":"20190221180522.vyoh6nxov4gupff6@ofb.net","subject":"Re: [PATCH 0/1] de-alphabetize command list","fromName":"","fromEmail":"frederik@ofb.net","sentAt":"2019-03-11T09:04:36Z","receivedAt":"2019-03-11T09:04:43Z","isPatch":true,"sender":{"key":"frederik@ofb.net","avatar":null},"body":"Hey Git people,\n\nI didn't get a reply and I'm not sure what the appropriate ping\ninterval is, or when I should conclude that no one is interested.\n\nThere seemed to be some vaguely positive feedback before I embarked on\nthis project. At the same time I don't want to pester anyone into\napplying patches in a disorganized fashion.\n\nI'm not subscribed to the mailing list so I apologize if I'm out of\ntune with a release cycle or current development thrust.\n\nThanks,\n\nFrederick\n\nOn Thu, Feb 21, 2019 at 10:05:22AM -0800, frederik@ofb.net wrote:\n>I realized that it would probably be easier to discuss this proposal\n>if I attached the final command listing and the rendered manual page.\n>Please find them attached to this message.\n>\n>Thank you,\n>\n>Frederick\n>\n>On Tue, Feb 19, 2019 at 09:54:12AM -0800, Frederick Eaton wrote:\n>>This is a follow-up to my proposal to de-alphabetize the command\n>>listings in the git(1) manual page, from 6 July 2018.\n>>\n>>Some projects have manual page items listed in alphabetical order,\n>>some don't. As I argued in my proposal, I find it easier to learn from\n>>material which is not alphabetized. If this patch is accepted, I hope\n>>that it will make the Git documentation more accessible to myself and\n>>others.\n>>\n>>I produced the reordered command list in this patch using several\n>>sources, as indicated by comments in the new command-list.txt file.\n>>First, all the commands in the main part of \"gittutorial(7)\" appear in\n>>order, then the commands in giteveryday(7). Then appear additional\n>>commands from a friend's shell history, in reverse order of frequency.\n>>Then gittutorial-2(7), then gitcore-tutorial(7). After that there is a\n>>list of \"guides\", followed by about 100 commands not appearing in the\n>>earlier lists. I kept the guides and the remaining commands in their\n>>category groupings (guide, mainporcelain, ancillarymanipulators,\n>>etc.), but ordered the commands within each category according to my\n>>own judgment after skimming each manual page.\n>>\n>>To verify that the new list is a permutation of the most recent list,\n>>I use the following command (it should produce no output and exit 0):\n>>\n>>   diff <(git show master:command-list.txt | grep -v '^#' | sort ) <(cat command-list.txt | grep -v '^#' | sort)\n>>\n>>Note this patch changes the order of commands appearing in the\n>>generated file \"command-list.h\", which mostly seems to be used by\n>>\"help.c\". Probably due to the various occurrences of QSORT in\n>>\"help.c\", I think this reordering has no visible effect. I am willing\n>>to do any additional testing which may be recommended to ensure that\n>>this patch has no undesired consequences.\n>>\n>>Frederick Eaton (1):\n>> Prioritize list of commands appearing in git(1), via command-list.txt.\n>>   Don't invoke 'sort' in Documentation/cmd-list.perl.\n>>\n>>Documentation/cmd-list.perl |   2 +-\n>>command-list.txt            | 295 +++++++++++++++++++-----------------\n>>2 files changed, 158 insertions(+), 139 deletions(-)\n>>\n>>-- \n>>2.20.1\n>>\n\n># Command classification list\n># ---------------------------\n># All supported commands, builtin or external, must be described in\n># here. This info is used to list commands in various places. Each\n># command is on one line followed by one or more attributes.\n>#\n># The first attribute group is mandatory and indicates the command\n># type. This group includes:\n>#\n>#   mainporcelain\n>#   ancillarymanipulators\n>#   ancillaryinterrogators\n>#   foreignscminterface\n>#   plumbingmanipulators\n>#   plumbinginterrogators\n>#   synchingrepositories\n>#   synchelpers\n>#   purehelpers\n>#\n># The type names are self explanatory. But if you want to see what\n># command belongs to what group to get a better picture, have a look\n># at \"git\" man page, \"GIT COMMANDS\" section.\n>#\n># Commands of type mainporcelain can also optionally have one of these\n># attributes:\n>#\n>#   init\n>#   worktree\n>#   info\n>#   history\n>#   remote\n>#\n># These commands are considered \"common\" and will show up in \"git\n># help\" output in groups. Uncommon porcelain commands must not\n># specify any of these attributes.\n>#\n># \"complete\" attribute is used to mark that the command should be\n># completable by git-completion.bash. Note that by default,\n># mainporcelain commands are completable so you don't need this\n># attribute.\n>#\n># As part of the Git man page list, the man(5/7) guides are also\n># specified here, which can only have \"guide\" attribute and nothing\n># else.\n>#\n># February 2019: This list had been sorted alphabetically but has been\n># reordered to make it easier for people to learn from the main git(1)\n># manual page. The new ordering is according to approximate usefulness\n># / frequency of use / order of use, with some grouping by topic. The\n># idea is to make it possible to read the manual page from beginning\n># to end and see the most important commands first, rather than\n># getting them in alphabetical order - in other words, to make the\n># manual page more like a table of contents and less like an index.\n># Please consider this when adding new commands.\n>#\n>### command list (do not change this line, also do not change alignment)\n># command name                          category [category] [category]\n># From gittutorial\n>git-help                                ancillaryinterrogators          complete\n>git-config                              ancillarymanipulators           complete\n>git-clone                               mainporcelain           init\n>git-init                                mainporcelain           init\n>git-add                                 mainporcelain           worktree\n>git-commit                              mainporcelain           history\n>git-diff                                mainporcelain           history\n>git-status                              mainporcelain           info\n>git-log                                 mainporcelain           info\n>git-branch                              mainporcelain           history\n>git-checkout                            mainporcelain           history\n>git-merge                               mainporcelain           history\n>gitk                                    mainporcelain\n>git-pull                                mainporcelain           remote\n>git-fetch                               mainporcelain           remote\n># From tutorial NEXT STEPS\n>git-format-patch                        mainporcelain\n>git-bisect                              mainporcelain           info\n>giteveryday                             guide\n>gitworkflows                            guide\n>gitcvs-migration                        guide\n># From giteveryday\n>git-reset                               mainporcelain           worktree\n>git-rebase                              mainporcelain           history\n>git-tag                                 mainporcelain           history\n>git-push                                mainporcelain           remote\n>git-send-email                          foreignscminterface             complete\n>git-request-pull                        foreignscminterface             complete\n>git-am                                  mainporcelain\n>git-revert                              mainporcelain\n>git-daemon                              synchingrepositories\n>git-shell                               synchelpers\n>git-http-backend                        synchingrepositories\n>gitweb                                  ancillaryinterrogators\n># From user feedback\n>git-grep                                mainporcelain           info\n>git-show                                mainporcelain           info\n>git-submodule                           mainporcelain\n>git-cherry-pick                         mainporcelain\n>git-clean                               mainporcelain\n># From gittutorial-2\n>git-cat-file                            plumbinginterrogators\n>git-ls-tree                             plumbinginterrogators\n>git-ls-files                            plumbinginterrogators\n>gitcore-tutorial                        guide\n>gitglossary                             guide\n># From gitcore-tutorial\n>git-update-index                        plumbingmanipulators\n>git-diff-files                          plumbinginterrogators\n>git-write-tree                          plumbingmanipulators\n>git-read-tree                           plumbingmanipulators\n>git-checkout-index                      plumbingmanipulators\n>git-show-branch                         ancillaryinterrogators          complete\n>git-name-rev                            plumbinginterrogators\n>git-merge-index                         plumbingmanipulators\n>git-repack                              ancillarymanipulators           complete\n>git-prune-packed                        plumbingmanipulators\n>git-update-server-info                  synchingrepositories\n>git-prune                               ancillarymanipulators\n>git-cherry                              plumbinginterrogators          complete\n># Guides, reordered\n>gittutorial                             guide\n>gittutorial-2                           guide\n>gitrevisions                            guide\n>gitignore                               guide\n>gitcli                                  guide\n>gitrepository-layout                    guide\n>gitdiffcore                             guide\n>gitmodules                              guide\n>githooks                                guide\n>gitnamespaces                           guide\n>gitattributes                           guide\n># All other commands, sorted by man page category and then by\n># approximate priority\n>git-stash                               mainporcelain\n>git-rm                                  mainporcelain           worktree\n>git-mv                                  mainporcelain           worktree\n>git-gui                                 mainporcelain\n>git-citool                              mainporcelain\n>git-archive                             mainporcelain\n>git-shortlog                            mainporcelain\n>git-describe                            mainporcelain\n>git-gc                                  mainporcelain\n>git-notes                               mainporcelain\n>git-worktree                            mainporcelain\n>git-bundle                              mainporcelain\n>git-range-diff                          mainporcelain\n>git-stage                                                               complete\n>git-reflog                              ancillarymanipulators           complete\n>git-remote                              ancillarymanipulators           complete\n>git-mergetool                           ancillarymanipulators           complete\n>git-filter-branch                       ancillarymanipulators\n>git-replace                             ancillarymanipulators           complete\n>git-fast-export                         ancillarymanipulators\n>git-fast-import                         ancillarymanipulators\n>git-pack-refs                           ancillarymanipulators\n>git-cvsimport                           foreignscminterface\n>git-cvsserver                           foreignscminterface\n>git-cvsexportcommit                     foreignscminterface\n>git-svn                                 foreignscminterface\n>git-p4                                  foreignscminterface\n>git-quiltimport                         foreignscminterface\n>git-archimport                          foreignscminterface\n>git-imap-send                           foreignscminterface\n>git-apply                               plumbingmanipulators            complete\n>git-merge-file                          plumbingmanipulators\n>git-mktag                               plumbingmanipulators\n>git-hash-object                         plumbingmanipulators\n>git-update-ref                          plumbingmanipulators\n>git-symbolic-ref                        plumbingmanipulators\n>git-commit-tree                         plumbingmanipulators\n>git-commit-graph                        plumbingmanipulators\n>git-mktree                              plumbingmanipulators\n>git-pack-objects                        plumbingmanipulators\n>git-unpack-objects                      plumbingmanipulators\n>git-index-pack                          plumbingmanipulators\n>git-multi-pack-index                    plumbingmanipulators\n>git-blame                               ancillaryinterrogators          complete\n>git-annotate                            ancillaryinterrogators\n>git-instaweb                            ancillaryinterrogators          complete\n>git-rerere                              ancillaryinterrogators\n>git-fsck                                ancillaryinterrogators          complete\n>git-whatchanged                         ancillaryinterrogators          complete\n>git-difftool                            ancillaryinterrogators          complete\n>git-merge-tree                          ancillaryinterrogators\n>git-count-objects                       ancillaryinterrogators\n>git-verify-commit                       ancillaryinterrogators\n>git-verify-tag                          ancillaryinterrogators\n>git-send-pack                           synchingrepositories\n>git-fetch-pack                          synchingrepositories\n>git-parse-remote                        synchelpers\n>git-receive-pack                        synchelpers\n>git-upload-pack                         synchelpers\n>git-upload-archive                      synchelpers\n>git-http-fetch                          synchelpers\n>git-http-push                           synchelpers\n>git-var                                 plumbinginterrogators\n>git-rev-list                            plumbinginterrogators\n>git-rev-parse                           plumbinginterrogators\n>git-for-each-ref                        plumbinginterrogators\n>git-show-ref                            plumbinginterrogators\n>git-ls-remote                           plumbinginterrogators\n>git-diff-tree                           plumbinginterrogators\n>git-diff-index                          plumbinginterrogators\n>git-merge-base                          plumbinginterrogators\n>git-verify-pack                         plumbinginterrogators\n>git-pack-redundant                      plumbinginterrogators\n>git-unpack-file                         plumbinginterrogators\n>git-show-index                          plumbinginterrogators\n>git-get-tar-commit-id                   plumbinginterrogators\n>git-merge-one-file                      purehelpers\n>git-sh-setup                            purehelpers\n>git-check-ref-format                    purehelpers\n>git-check-ignore                        purehelpers\n>git-check-attr                          purehelpers\n>git-credential                          purehelpers\n>git-credential-cache                    purehelpers\n>git-credential-store                    purehelpers\n>git-fmt-merge-msg                       purehelpers\n>git-check-mailmap                       purehelpers\n>git-mailsplit                           purehelpers\n>git-mailinfo                            purehelpers\n>git-interpret-trailers                  purehelpers\n>git-column                              purehelpers\n>git-stripspace                          purehelpers\n>git-patch-id                            purehelpers\n>git-sh-i18n                             purehelpers\n\n>GIT(1)                            Git Manual                            GIT(1)\n>\n>NAME\n>       git - the stupid content tracker\n>\n>SYNOPSIS\n>       git [--version] [--help] [-C <path>] [-c <name>=<value>]\n>           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\n>           [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]\n>           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\n>           [--super-prefix=<path>]\n>           <command> [<args>]\n>\n>DESCRIPTION\n>       Git is a fast, scalable, distributed revision control system with an\n>       unusually rich command set that provides both high-level operations and\n>       full access to internals.\n>\n>       See gittutorial(7) to get started, then see giteveryday(7) for a useful\n>       minimum set of commands. The Git User's Manual[1] has a more in-depth\n>       introduction.\n>\n>       After you mastered the basic concepts, you can come back to this page\n>       to learn what commands Git offers. You can learn more about individual\n>       Git commands with \"git help command\". gitcli(7) manual page gives you\n>       an overview of the command-line command syntax.\n>\n>       A formatted and hyperlinked copy of the latest Git documentation can be\n>       viewed at https://git.github.io/htmldocs/git.html.\n>\n>OPTIONS\n>       --version\n>           Prints the Git suite version that the git program came from.\n>\n>       --help\n>           Prints the synopsis and a list of the most commonly used commands.\n>           If the option --all or -a is given then all available commands are\n>           printed. If a Git command is named this option will bring up the\n>           manual page for that command.\n>\n>           Other options are available to control how the manual page is\n>           displayed. See git-help(1) for more information, because git --help\n>           ...  is converted internally into git help ....\n>\n>       -C <path>\n>           Run as if git was started in <path> instead of the current working\n>           directory. When multiple -C options are given, each subsequent\n>           non-absolute -C <path> is interpreted relative to the preceding -C\n>           <path>.\n>\n>           This option affects options that expect path name like --git-dir\n>           and --work-tree in that their interpretations of the path names\n>           would be made relative to the working directory caused by the -C\n>           option. For example the following invocations are equivalent:\n>\n>               git --git-dir=a.git --work-tree=b -C c status\n>               git --git-dir=c/a.git --work-tree=c/b status\n>\n>       -c <name>=<value>\n>           Pass a configuration parameter to the command. The value given will\n>           override values from configuration files. The <name> is expected in\n>           the same format as listed by git config (subkeys separated by\n>           dots).\n>\n>           Note that omitting the = in git -c foo.bar ...  is allowed and sets\n>           foo.bar to the boolean true value (just like [foo]bar would in a\n>           config file). Including the equals but with an empty value (like\n>           git -c foo.bar= ...) sets foo.bar to the empty string which git\n>           config --type=bool will convert to false.\n>\n>       --exec-path[=<path>]\n>           Path to wherever your core Git programs are installed. This can\n>           also be controlled by setting the GIT_EXEC_PATH environment\n>           variable. If no path is given, git will print the current setting\n>           and then exit.\n>\n>       --html-path\n>           Print the path, without trailing slash, where Git's HTML\n>           documentation is installed and exit.\n>\n>       --man-path\n>           Print the manpath (see man(1)) for the man pages for this version\n>           of Git and exit.\n>\n>       --info-path\n>           Print the path where the Info files documenting this version of Git\n>           are installed and exit.\n>\n>       -p, --paginate\n>           Pipe all output into less (or if set, $PAGER) if standard output is\n>           a terminal. This overrides the pager.<cmd> configuration options\n>           (see the \"Configuration Mechanism\" section below).\n>\n>       -P, --no-pager\n>           Do not pipe Git output into a pager.\n>\n>       --git-dir=<path>\n>           Set the path to the repository. This can also be controlled by\n>           setting the GIT_DIR environment variable. It can be an absolute\n>           path or relative path to current working directory.\n>\n>       --work-tree=<path>\n>           Set the path to the working tree. It can be an absolute path or a\n>           path relative to the current working directory. This can also be\n>           controlled by setting the GIT_WORK_TREE environment variable and\n>           the core.worktree configuration variable (see core.worktree in git-\n>           config(1) for a more detailed discussion).\n>\n>       --namespace=<path>\n>           Set the Git namespace. See gitnamespaces(7) for more details.\n>           Equivalent to setting the GIT_NAMESPACE environment variable.\n>\n>       --super-prefix=<path>\n>           Currently for internal use only. Set a prefix which gives a path\n>           from above a repository down to its root. One use is to give\n>           submodules context about the superproject that invoked it.\n>\n>       --bare\n>           Treat the repository as a bare repository. If GIT_DIR environment\n>           is not set, it is set to the current working directory.\n>\n>       --no-replace-objects\n>           Do not use replacement refs to replace Git objects. See git-\n>           replace(1) for more information.\n>\n>       --literal-pathspecs\n>           Treat pathspecs literally (i.e. no globbing, no pathspec magic).\n>           This is equivalent to setting the GIT_LITERAL_PATHSPECS environment\n>           variable to 1.\n>\n>       --glob-pathspecs\n>           Add \"glob\" magic to all pathspec. This is equivalent to setting the\n>           GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on\n>           individual pathspecs can be done using pathspec magic \":(literal)\"\n>\n>       --noglob-pathspecs\n>           Add \"literal\" magic to all pathspec. This is equivalent to setting\n>           the GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling\n>           globbing on individual pathspecs can be done using pathspec magic\n>           \":(glob)\"\n>\n>       --icase-pathspecs\n>           Add \"icase\" magic to all pathspec. This is equivalent to setting\n>           the GIT_ICASE_PATHSPECS environment variable to 1.\n>\n>       --no-optional-locks\n>           Do not perform optional operations that require locks. This is\n>           equivalent to setting the GIT_OPTIONAL_LOCKS to 0.\n>\n>       --list-cmds=group[,group...]\n>           List commands by group. This is an internal/experimental option and\n>           may change or be removed in the future. Supported groups are:\n>           builtins, parseopt (builtin commands that use parse-options), main\n>           (all commands in libexec directory), others (all other commands in\n>           $PATH that have git- prefix), list-<category> (see categories in\n>           command-list.txt), nohelpers (exclude helper commands), alias and\n>           config (retrieve command list from config variable\n>           completion.commands)\n>\n>GIT COMMANDS\n>       We divide Git into high level (\"porcelain\") commands and low level\n>       (\"plumbing\") commands.\n>\n>HIGH-LEVEL COMMANDS (PORCELAIN)\n>       We separate the porcelain commands into the main commands and some\n>       ancillary user utilities.\n>\n>   Main porcelain commands\n>       git-clone(1)\n>           Clone a repository into a new directory.\n>\n>       git-init(1)\n>           Create an empty Git repository or reinitialize an existing one.\n>\n>       git-add(1)\n>           Add file contents to the index.\n>\n>       git-commit(1)\n>           Record changes to the repository.\n>\n>       git-diff(1)\n>           Show changes between commits, commit and working tree, etc.\n>\n>       git-status(1)\n>           Show the working tree status.\n>\n>       git-log(1)\n>           Show commit logs.\n>\n>       git-branch(1)\n>           List, create, or delete branches.\n>\n>       git-checkout(1)\n>           Switch branches or restore working tree files.\n>\n>       git-merge(1)\n>           Join two or more development histories together.\n>\n>       gitk(1)\n>           The Git repository browser.\n>\n>       git-pull(1)\n>           Fetch from and integrate with another repository or a local branch.\n>\n>       git-fetch(1)\n>           Download objects and refs from another repository.\n>\n>       git-format-patch(1)\n>           Prepare patches for e-mail submission.\n>\n>       git-bisect(1)\n>           Use binary search to find the commit that introduced a bug.\n>\n>       git-reset(1)\n>           Reset current HEAD to the specified state.\n>\n>       git-rebase(1)\n>           Reapply commits on top of another base tip.\n>\n>       git-tag(1)\n>           Create, list, delete or verify a tag object signed with GPG.\n>\n>       git-push(1)\n>           Update remote refs along with associated objects.\n>\n>       git-am(1)\n>           Apply a series of patches from a mailbox.\n>\n>       git-revert(1)\n>           Revert some existing commits.\n>\n>       git-grep(1)\n>           Print lines matching a pattern.\n>\n>       git-show(1)\n>           Show various types of objects.\n>\n>       git-submodule(1)\n>           Initialize, update or inspect submodules.\n>\n>       git-cherry-pick(1)\n>           Apply the changes introduced by some existing commits.\n>\n>       git-clean(1)\n>           Remove untracked files from the working tree.\n>\n>       git-stash(1)\n>           Stash the changes in a dirty working directory away.\n>\n>       git-rm(1)\n>           Remove files from the working tree and from the index.\n>\n>       git-mv(1)\n>           Move or rename a file, a directory, or a symlink.\n>\n>       git-gui(1)\n>           A portable graphical interface to Git.\n>\n>       git-citool(1)\n>           Graphical alternative to git-commit.\n>\n>       git-archive(1)\n>           Create an archive of files from a named tree.\n>\n>       git-shortlog(1)\n>           Summarize git log output.\n>\n>       git-describe(1)\n>           Give an object a human readable name based on an available ref.\n>\n>       git-gc(1)\n>           Cleanup unnecessary files and optimize the local repository.\n>\n>       git-notes(1)\n>           Add or inspect object notes.\n>\n>       git-worktree(1)\n>           Manage multiple working trees.\n>\n>       git-bundle(1)\n>           Move objects and refs by archive.\n>\n>       git-range-diff(1)\n>           Compare two commit ranges (e.g. two versions of a branch).\n>\n>   Ancillary Commands\n>       Manipulators:\n>\n>       git-config(1)\n>           Get and set repository or global options.\n>\n>       git-repack(1)\n>           Pack unpacked objects in a repository.\n>\n>       git-prune(1)\n>           Prune all unreachable objects from the object database.\n>\n>       git-reflog(1)\n>           Manage reflog information.\n>\n>       git-remote(1)\n>           Manage set of tracked repositories.\n>\n>       git-mergetool(1)\n>           Run merge conflict resolution tools to resolve merge conflicts.\n>\n>       git-filter-branch(1)\n>           Rewrite branches.\n>\n>       git-replace(1)\n>           Create, list, delete refs to replace objects.\n>\n>       git-fast-export(1)\n>           Git data exporter.\n>\n>       git-fast-import(1)\n>           Backend for fast Git data importers.\n>\n>       git-pack-refs(1)\n>           Pack heads and tags for efficient repository access.\n>\n>       Interrogators:\n>\n>       git-help(1)\n>           Display help information about Git.\n>\n>       gitweb(1)\n>           Git web interface (web frontend to Git repositories).\n>\n>       git-show-branch(1)\n>           Show branches and their commits.\n>\n>       git-blame(1)\n>           Show what revision and author last modified each line of a file.\n>\n>       git-annotate(1)\n>           Annotate file lines with commit information.\n>\n>       git-instaweb(1)\n>           Instantly browse your working repository in gitweb.\n>\n>       git-rerere(1)\n>           Reuse recorded resolution of conflicted merges.\n>\n>       git-fsck(1)\n>           Verifies the connectivity and validity of the objects in the\n>           database.\n>\n>       git-whatchanged(1)\n>           Show logs with difference each commit introduces.\n>\n>       git-difftool(1)\n>           Show changes using common diff tools.\n>\n>       git-merge-tree(1)\n>           Show three-way merge without touching index.\n>\n>       git-count-objects(1)\n>           Count unpacked number of objects and their disk consumption.\n>\n>       git-verify-commit(1)\n>           Check the GPG signature of commits.\n>\n>       git-verify-tag(1)\n>           Check the GPG signature of tags.\n>\n>   Interacting with Others\n>       These commands are to interact with foreign SCM and with other people\n>       via patch over e-mail.\n>\n>       git-send-email(1)\n>           Send a collection of patches as emails.\n>\n>       git-request-pull(1)\n>           Generates a summary of pending changes.\n>\n>       git-cvsimport(1)\n>           Salvage your data out of another SCM people love to hate.\n>\n>       git-cvsserver(1)\n>           A CVS server emulator for Git.\n>\n>       git-cvsexportcommit(1)\n>           Export a single commit to a CVS checkout.\n>\n>       git-svn(1)\n>           Bidirectional operation between a Subversion repository and Git.\n>\n>       git-p4(1)\n>           Import from and submit to Perforce repositories.\n>\n>       git-quiltimport(1)\n>           Applies a quilt patchset onto the current branch.\n>\n>       git-archimport(1)\n>           Import a GNU Arch repository into Git.\n>\n>       git-imap-send(1)\n>           Send a collection of patches from stdin to an IMAP folder.\n>\n>LOW-LEVEL COMMANDS (PLUMBING)\n>       Although Git includes its own porcelain layer, its low-level commands\n>       are sufficient to support development of alternative porcelains.\n>       Developers of such porcelains might start by reading about git-update-\n>       index(1) and git-read-tree(1).\n>\n>       The interface (input, output, set of options and the semantics) to\n>       these low-level commands are meant to be a lot more stable than\n>       Porcelain level commands, because these commands are primarily for\n>       scripted use. The interface to Porcelain commands on the other hand are\n>       subject to change in order to improve the end user experience.\n>\n>       The following description divides the low-level commands into commands\n>       that manipulate objects (in the repository, index, and working tree),\n>       commands that interrogate and compare objects, and commands that move\n>       objects and references between repositories.\n>\n>   Manipulation commands\n>       git-update-index(1)\n>           Register file contents in the working tree to the index.\n>\n>       git-write-tree(1)\n>           Create a tree object from the current index.\n>\n>       git-read-tree(1)\n>           Reads tree information into the index.\n>\n>       git-checkout-index(1)\n>           Copy files from the index to the working tree.\n>\n>       git-merge-index(1)\n>           Run a merge for files needing merging.\n>\n>       git-prune-packed(1)\n>           Remove extra objects that are already in pack files.\n>\n>       git-apply(1)\n>           Apply a patch to files and/or to the index.\n>\n>       git-merge-file(1)\n>           Run a three-way file merge.\n>\n>       git-mktag(1)\n>           Creates a tag object.\n>\n>       git-hash-object(1)\n>           Compute object ID and optionally creates a blob from a file.\n>\n>       git-update-ref(1)\n>           Update the object name stored in a ref safely.\n>\n>       git-symbolic-ref(1)\n>           Read, modify and delete symbolic refs.\n>\n>       git-commit-tree(1)\n>           Create a new commit object.\n>\n>       git-commit-graph(1)\n>           Write and verify Git commit-graph files.\n>\n>       git-mktree(1)\n>           Build a tree-object from ls-tree formatted text.\n>\n>       git-pack-objects(1)\n>           Create a packed archive of objects.\n>\n>       git-unpack-objects(1)\n>           Unpack objects from a packed archive.\n>\n>       git-index-pack(1)\n>           Build pack index file for an existing packed archive.\n>\n>       git-multi-pack-index(1)\n>           Write and verify multi-pack-indexes.\n>\n>   Interrogation commands\n>       git-cat-file(1)\n>           Provide content or type and size information for repository\n>           objects.\n>\n>       git-ls-tree(1)\n>           List the contents of a tree object.\n>\n>       git-ls-files(1)\n>           Show information about files in the index and the working tree.\n>\n>       git-diff-files(1)\n>           Compares files in the working tree and the index.\n>\n>       git-name-rev(1)\n>           Find symbolic names for given revs.\n>\n>       git-cherry(1)\n>           Find commits yet to be applied to upstream.\n>\n>       git-var(1)\n>           Show a Git logical variable.\n>\n>       git-rev-list(1)\n>           Lists commit objects in reverse chronological order.\n>\n>       git-rev-parse(1)\n>           Pick out and massage parameters.\n>\n>       git-for-each-ref(1)\n>           Output information on each ref.\n>\n>       git-show-ref(1)\n>           List references in a local repository.\n>\n>       git-ls-remote(1)\n>           List references in a remote repository.\n>\n>       git-diff-tree(1)\n>           Compares the content and mode of blobs found via two tree objects.\n>\n>       git-diff-index(1)\n>           Compare a tree to the working tree or index.\n>\n>       git-merge-base(1)\n>           Find as good common ancestors as possible for a merge.\n>\n>       git-verify-pack(1)\n>           Validate packed Git archive files.\n>\n>       git-pack-redundant(1)\n>           Find redundant pack files.\n>\n>       git-unpack-file(1)\n>           Creates a temporary file with a blob's contents.\n>\n>       git-show-index(1)\n>           Show packed archive index.\n>\n>       git-get-tar-commit-id(1)\n>           Extract commit ID from an archive created using git-archive.\n>\n>       In general, the interrogate commands do not touch the files in the\n>       working tree.\n>\n>   Synching repositories\n>       git-daemon(1)\n>           A really simple server for Git repositories.\n>\n>       git-http-backend(1)\n>           Server side implementation of Git over HTTP.\n>\n>       git-update-server-info(1)\n>           Update auxiliary info file to help dumb servers.\n>\n>       git-send-pack(1)\n>           Push objects over Git protocol to another repository.\n>\n>       git-fetch-pack(1)\n>           Receive missing objects from another repository.\n>\n>       The following are helper commands used by the above; end users\n>       typically do not use them directly.\n>\n>       git-shell(1)\n>           Restricted login shell for Git-only SSH access.\n>\n>       git-parse-remote(1)\n>           Routines to help parsing remote repository access parameters.\n>\n>       git-receive-pack(1)\n>           Receive what is pushed into the repository.\n>\n>       git-upload-pack(1)\n>           Send objects packed back to git-fetch-pack.\n>\n>       git-upload-archive(1)\n>           Send archive back to git-archive.\n>\n>       git-http-fetch(1)\n>           Download from a remote Git repository via HTTP.\n>\n>       git-http-push(1)\n>           Push objects over HTTP/DAV to another repository.\n>\n>   Internal helper commands\n>       These are internal helper commands used by other commands; end users\n>       typically do not use them directly.\n>\n>       git-merge-one-file(1)\n>           The standard helper program to use with git-merge-index.\n>\n>       git-sh-setup(1)\n>           Common Git shell script setup code.\n>\n>       git-check-ref-format(1)\n>           Ensures that a reference name is well formed.\n>\n>       git-check-ignore(1)\n>           Debug gitignore / exclude files.\n>\n>       git-check-attr(1)\n>           Display gitattributes information.\n>\n>       git-credential(1)\n>           Retrieve and store user credentials.\n>\n>       git-credential-cache(1)\n>           Helper to temporarily store passwords in memory.\n>\n>       git-credential-store(1)\n>           Helper to store credentials on disk.\n>\n>       git-fmt-merge-msg(1)\n>           Produce a merge commit message.\n>\n>       git-check-mailmap(1)\n>           Show canonical names and email addresses of contacts.\n>\n>       git-mailsplit(1)\n>           Simple UNIX mbox splitter program.\n>\n>       git-mailinfo(1)\n>           Extracts patch and authorship from a single e-mail message.\n>\n>       git-interpret-trailers(1)\n>           add or parse structured information in commit messages.\n>\n>       git-column(1)\n>           Display data in columns.\n>\n>       git-stripspace(1)\n>           Remove unnecessary whitespace.\n>\n>       git-patch-id(1)\n>           Compute unique ID for a patch.\n>\n>       git-sh-i18n(1)\n>           Git's i18n setup code for shell scripts.\n>\n>CONFIGURATION MECHANISM\n>       Git uses a simple text format to store customizations that are per\n>       repository and are per user. Such a configuration file may look like\n>       this:\n>\n>           #\n>           # A '#' or ';' character indicates a comment.\n>           #\n>\n>           ; core variables\n>           [core]\n>                   ; Don't trust file modes\n>                   filemode = false\n>\n>           ; user identity\n>           [user]\n>                   name = \"Junio C Hamano\"\n>                   email = \"gitster@pobox.com\"\n>\n>       Various commands read from the configuration file and adjust their\n>       operation accordingly. See git-config(1) for a list and more details\n>       about the configuration mechanism.\n>\n>IDENTIFIER TERMINOLOGY\n>       <object>\n>           Indicates the object name for any type of object.\n>\n>       <blob>\n>           Indicates a blob object name.\n>\n>       <tree>\n>           Indicates a tree object name.\n>\n>       <commit>\n>           Indicates a commit object name.\n>\n>       <tree-ish>\n>           Indicates a tree, commit or tag object name. A command that takes a\n>           <tree-ish> argument ultimately wants to operate on a <tree> object\n>           but automatically dereferences <commit> and <tag> objects that\n>           point at a <tree>.\n>\n>       <commit-ish>\n>           Indicates a commit or tag object name. A command that takes a\n>           <commit-ish> argument ultimately wants to operate on a <commit>\n>           object but automatically dereferences <tag> objects that point at a\n>           <commit>.\n>\n>       <type>\n>           Indicates that an object type is required. Currently one of: blob,\n>           tree, commit, or tag.\n>\n>       <file>\n>           Indicates a filename - almost always relative to the root of the\n>           tree structure GIT_INDEX_FILE describes.\n>\n>SYMBOLIC IDENTIFIERS\n>       Any Git command accepting any <object> can also use the following\n>       symbolic notation:\n>\n>       HEAD\n>           indicates the head of the current branch.\n>\n>       <tag>\n>           a valid tag name (i.e. a refs/tags/<tag> reference).\n>\n>       <head>\n>           a valid head name (i.e. a refs/heads/<head> reference).\n>\n>       For a more complete list of ways to spell object names, see \"SPECIFYING\n>       REVISIONS\" section in gitrevisions(7).\n>\n>FILE/DIRECTORY STRUCTURE\n>       Please see the gitrepository-layout(5) document.\n>\n>       Read githooks(5) for more details about each hook.\n>\n>       Higher level SCMs may provide and manage additional information in the\n>       $GIT_DIR.\n>\n>TERMINOLOGY\n>       Please see gitglossary(7).\n>\n>ENVIRONMENT VARIABLES\n>       Various Git commands use the following environment variables:\n>\n>   The Git Repository\n>       These environment variables apply to all core Git commands. Nb: it is\n>       worth noting that they may be used/overridden by SCMS sitting above Git\n>       so take care if using a foreign front-end.\n>\n>       GIT_INDEX_FILE\n>           This environment allows the specification of an alternate index\n>           file. If not specified, the default of $GIT_DIR/index is used.\n>\n>       GIT_INDEX_VERSION\n>           This environment variable allows the specification of an index\n>           version for new repositories. It won't affect existing index files.\n>           By default index file version 2 or 3 is used. See git-update-\n>           index(1) for more information.\n>\n>       GIT_OBJECT_DIRECTORY\n>           If the object storage directory is specified via this environment\n>           variable then the sha1 directories are created underneath -\n>           otherwise the default $GIT_DIR/objects directory is used.\n>\n>       GIT_ALTERNATE_OBJECT_DIRECTORIES\n>           Due to the immutable nature of Git objects, old objects can be\n>           archived into shared, read-only directories. This variable\n>           specifies a \":\" separated (on Windows \";\" separated) list of Git\n>           object directories which can be used to search for Git objects. New\n>           objects will not be written to these directories.\n>\n>           Entries that begin with \" (double-quote) will be interpreted as\n>           C-style quoted paths, removing leading and trailing double-quotes\n>           and respecting backslash escapes. E.g., the value\n>           \"path-with-\\\"-and-:-in-it\":vanilla-path has two paths:\n>           path-with-\"-and-:-in-it and vanilla-path.\n>\n>       GIT_DIR\n>           If the GIT_DIR environment variable is set then it specifies a path\n>           to use instead of the default .git for the base of the repository.\n>           The --git-dir command-line option also sets this value.\n>\n>       GIT_WORK_TREE\n>           Set the path to the root of the working tree. This can also be\n>           controlled by the --work-tree command-line option and the\n>           core.worktree configuration variable.\n>\n>       GIT_NAMESPACE\n>           Set the Git namespace; see gitnamespaces(7) for details. The\n>           --namespace command-line option also sets this value.\n>\n>       GIT_CEILING_DIRECTORIES\n>           This should be a colon-separated list of absolute paths. If set, it\n>           is a list of directories that Git should not chdir up into while\n>           looking for a repository directory (useful for excluding\n>           slow-loading network directories). It will not exclude the current\n>           working directory or a GIT_DIR set on the command line or in the\n>           environment. Normally, Git has to read the entries in this list and\n>           resolve any symlink that might be present in order to compare them\n>           with the current directory. However, if even this access is slow,\n>           you can add an empty entry to the list to tell Git that the\n>           subsequent entries are not symlinks and needn't be resolved; e.g.,\n>           GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink.\n>\n>       GIT_DISCOVERY_ACROSS_FILESYSTEM\n>           When run in a directory that does not have \".git\" repository\n>           directory, Git tries to find such a directory in the parent\n>           directories to find the top of the working tree, but by default it\n>           does not cross filesystem boundaries. This environment variable can\n>           be set to true to tell Git not to stop at filesystem boundaries.\n>           Like GIT_CEILING_DIRECTORIES, this will not affect an explicit\n>           repository directory set via GIT_DIR or on the command line.\n>\n>       GIT_COMMON_DIR\n>           If this variable is set to a path, non-worktree files that are\n>           normally in $GIT_DIR will be taken from this path instead.\n>           Worktree-specific files such as HEAD or index are taken from\n>           $GIT_DIR. See gitrepository-layout(5) and git-worktree(1) for\n>           details. This variable has lower precedence than other path\n>           variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...\n>\n>   Git Commits\n>       GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME,\n>       GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, EMAIL\n>           see git-commit-tree(1)\n>\n>   Git Diffs\n>       GIT_DIFF_OPTS\n>           Only valid setting is \"--unified=??\" or \"-u??\" to set the number of\n>           context lines shown when a unified diff is created. This takes\n>           precedence over any \"-U\" or \"--unified\" option value passed on the\n>           Git diff command line.\n>\n>       GIT_EXTERNAL_DIFF\n>           When the environment variable GIT_EXTERNAL_DIFF is set, the program\n>           named by it is called, instead of the diff invocation described\n>           above. For a path that is added, removed, or modified,\n>           GIT_EXTERNAL_DIFF is called with 7 parameters:\n>\n>               path old-file old-hex old-mode new-file new-hex new-mode\n>\n>           where:\n>\n>       <old|new>-file\n>           are files GIT_EXTERNAL_DIFF can use to read the contents of\n>           <old|new>,\n>\n>       <old|new>-hex\n>           are the 40-hexdigit SHA-1 hashes,\n>\n>       <old|new>-mode\n>           are the octal representation of the file modes.\n>\n>           The file parameters can point at the user's working file (e.g.\n>           new-file in \"git-diff-files\"), /dev/null (e.g.  old-file when a new\n>           file is added), or a temporary file (e.g.  old-file in the index).\n>           GIT_EXTERNAL_DIFF should not worry about unlinking the temporary\n>           file --- it is removed when GIT_EXTERNAL_DIFF exits.\n>\n>           For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1\n>           parameter, <path>.\n>\n>           For each path GIT_EXTERNAL_DIFF is called, two environment\n>           variables, GIT_DIFF_PATH_COUNTER and GIT_DIFF_PATH_TOTAL are set.\n>\n>       GIT_DIFF_PATH_COUNTER\n>           A 1-based counter incremented by one for every path.\n>\n>       GIT_DIFF_PATH_TOTAL\n>           The total number of paths.\n>\n>   other\n>       GIT_MERGE_VERBOSITY\n>           A number controlling the amount of output shown by the recursive\n>           merge strategy. Overrides merge.verbosity. See git-merge(1)\n>\n>       GIT_PAGER\n>           This environment variable overrides $PAGER. If it is set to an\n>           empty string or to the value \"cat\", Git will not launch a pager.\n>           See also the core.pager option in git-config(1).\n>\n>       GIT_EDITOR\n>           This environment variable overrides $EDITOR and $VISUAL. It is used\n>           by several Git commands when, on interactive mode, an editor is to\n>           be launched. See also git-var(1) and the core.editor option in git-\n>           config(1).\n>\n>       GIT_SSH, GIT_SSH_COMMAND\n>           If either of these environment variables is set then git fetch and\n>           git push will use the specified command instead of ssh when they\n>           need to connect to a remote system. The command-line parameters\n>           passed to the configured command are determined by the ssh variant.\n>           See ssh.variant option in git-config(1) for details.\n>\n>       + $GIT_SSH_COMMAND takes precedence over $GIT_SSH, and is interpreted\n>       by the shell, which allows additional arguments to be included.\n>       $GIT_SSH on the other hand must be just the path to a program (which\n>       can be a wrapper shell script, if additional arguments are needed).\n>\n>       + Usually it is easier to configure any desired options through your\n>       personal .ssh/config file. Please consult your ssh documentation for\n>       further details.\n>\n>       GIT_SSH_VARIANT\n>           If this environment variable is set, it overrides Git's\n>           autodetection whether GIT_SSH/GIT_SSH_COMMAND/core.sshCommand refer\n>           to OpenSSH, plink or tortoiseplink. This variable overrides the\n>           config setting ssh.variant that serves the same purpose.\n>\n>       GIT_ASKPASS\n>           If this environment variable is set, then Git commands which need\n>           to acquire passwords or passphrases (e.g. for HTTP or IMAP\n>           authentication) will call this program with a suitable prompt as\n>           command-line argument and read the password from its STDOUT. See\n>           also the core.askPass option in git-config(1).\n>\n>       GIT_TERMINAL_PROMPT\n>           If this environment variable is set to 0, git will not prompt on\n>           the terminal (e.g., when asking for HTTP authentication).\n>\n>       GIT_CONFIG_NOSYSTEM\n>           Whether to skip reading settings from the system-wide\n>           $(prefix)/etc/gitconfig file. This environment variable can be used\n>           along with $HOME and $XDG_CONFIG_HOME to create a predictable\n>           environment for a picky script, or you can set it temporarily to\n>           avoid using a buggy /etc/gitconfig file while waiting for someone\n>           with sufficient permissions to fix it.\n>\n>       GIT_FLUSH\n>           If this environment variable is set to \"1\", then commands such as\n>           git blame (in incremental mode), git rev-list, git log, git\n>           check-attr and git check-ignore will force a flush of the output\n>           stream after each record have been flushed. If this variable is set\n>           to \"0\", the output of these commands will be done using completely\n>           buffered I/O. If this environment variable is not set, Git will\n>           choose buffered or record-oriented flushing based on whether stdout\n>           appears to be redirected to a file or not.\n>\n>       GIT_TRACE\n>           Enables general trace messages, e.g. alias expansion, built-in\n>           command execution and external command execution.\n>\n>           If this variable is set to \"1\", \"2\" or \"true\" (comparison is case\n>           insensitive), trace messages will be printed to stderr.\n>\n>           If the variable is set to an integer value greater than 2 and lower\n>           than 10 (strictly) then Git will interpret this value as an open\n>           file descriptor and will try to write the trace messages into this\n>           file descriptor.\n>\n>           Alternatively, if the variable is set to an absolute path (starting\n>           with a / character), Git will interpret this as a file path and\n>           will try to append the trace messages to it.\n>\n>           Unsetting the variable, or setting it to empty, \"0\" or \"false\"\n>           (case insensitive) disables trace messages.\n>\n>       GIT_TRACE_FSMONITOR\n>           Enables trace messages for the filesystem monitor extension. See\n>           GIT_TRACE for available trace output options.\n>\n>       GIT_TRACE_PACK_ACCESS\n>           Enables trace messages for all accesses to any packs. For each\n>           access, the pack file name and an offset in the pack is recorded.\n>           This may be helpful for troubleshooting some pack-related\n>           performance problems. See GIT_TRACE for available trace output\n>           options.\n>\n>       GIT_TRACE_PACKET\n>           Enables trace messages for all packets coming in or out of a given\n>           program. This can help with debugging object negotiation or other\n>           protocol issues. Tracing is turned off at a packet starting with\n>           \"PACK\" (but see GIT_TRACE_PACKFILE below). See GIT_TRACE for\n>           available trace output options.\n>\n>       GIT_TRACE_PACKFILE\n>           Enables tracing of packfiles sent or received by a given program.\n>           Unlike other trace output, this trace is verbatim: no headers, and\n>           no quoting of binary data. You almost certainly want to direct into\n>           a file (e.g., GIT_TRACE_PACKFILE=/tmp/my.pack) rather than\n>           displaying it on the terminal or mixing it with other trace output.\n>\n>           Note that this is currently only implemented for the client side of\n>           clones and fetches.\n>\n>       GIT_TRACE_PERFORMANCE\n>           Enables performance related trace messages, e.g. total execution\n>           time of each Git command. See GIT_TRACE for available trace output\n>           options.\n>\n>       GIT_TRACE_SETUP\n>           Enables trace messages printing the .git, working tree and current\n>           working directory after Git has completed its setup phase. See\n>           GIT_TRACE for available trace output options.\n>\n>       GIT_TRACE_SHALLOW\n>           Enables trace messages that can help debugging fetching / cloning\n>           of shallow repositories. See GIT_TRACE for available trace output\n>           options.\n>\n>       GIT_TRACE_CURL\n>           Enables a curl full trace dump of all incoming and outgoing data,\n>           including descriptive information, of the git transport protocol.\n>           This is similar to doing curl --trace-ascii on the command line.\n>           This option overrides setting the GIT_CURL_VERBOSE environment\n>           variable. See GIT_TRACE for available trace output options.\n>\n>       GIT_TRACE_CURL_NO_DATA\n>           When a curl trace is enabled (see GIT_TRACE_CURL above), do not\n>           dump data (that is, only dump info lines and headers).\n>\n>       GIT_REDACT_COOKIES\n>           This can be set to a comma-separated list of strings. When a curl\n>           trace is enabled (see GIT_TRACE_CURL above), whenever a \"Cookies:\"\n>           header sent by the client is dumped, values of cookies whose key is\n>           in that list (case-sensitive) are redacted.\n>\n>       GIT_LITERAL_PATHSPECS\n>           Setting this variable to 1 will cause Git to treat all pathspecs\n>           literally, rather than as glob patterns. For example, running\n>           GIT_LITERAL_PATHSPECS=1 git log -- '*.c' will search for commits\n>           that touch the path *.c, not any paths that the glob *.c matches.\n>           You might want this if you are feeding literal paths to Git (e.g.,\n>           paths previously given to you by git ls-tree, --raw diff output,\n>           etc).\n>\n>       GIT_GLOB_PATHSPECS\n>           Setting this variable to 1 will cause Git to treat all pathspecs as\n>           glob patterns (aka \"glob\" magic).\n>\n>       GIT_NOGLOB_PATHSPECS\n>           Setting this variable to 1 will cause Git to treat all pathspecs as\n>           literal (aka \"literal\" magic).\n>\n>       GIT_ICASE_PATHSPECS\n>           Setting this variable to 1 will cause Git to treat all pathspecs as\n>           case-insensitive.\n>\n>       GIT_REFLOG_ACTION\n>           When a ref is updated, reflog entries are created to keep track of\n>           the reason why the ref was updated (which is typically the name of\n>           the high-level command that updated the ref), in addition to the\n>           old and new values of the ref. A scripted Porcelain command can use\n>           set_reflog_action helper function in git-sh-setup to set its name\n>           to this variable when it is invoked as the top level command by the\n>           end user, to be recorded in the body of the reflog.\n>\n>       GIT_REF_PARANOIA\n>           If set to 1, include broken or badly named refs when iterating over\n>           lists of refs. In a normal, non-corrupted repository, this does\n>           nothing. However, enabling it may help git to detect and abort some\n>           operations in the presence of broken refs. Git sets this variable\n>           automatically when performing destructive operations like git-\n>           prune(1). You should not need to set it yourself unless you want to\n>           be paranoid about making sure an operation has touched every ref\n>           (e.g., because you are cloning a repository to make a backup).\n>\n>       GIT_ALLOW_PROTOCOL\n>           If set to a colon-separated list of protocols, behave as if\n>           protocol.allow is set to never, and each of the listed protocols\n>           has protocol.<name>.allow set to always (overriding any existing\n>           configuration). In other words, any protocol not mentioned will be\n>           disallowed (i.e., this is a whitelist, not a blacklist). See the\n>           description of protocol.allow in git-config(1) for more details.\n>\n>       GIT_PROTOCOL_FROM_USER\n>           Set to 0 to prevent protocols used by fetch/push/clone which are\n>           configured to the user state. This is useful to restrict recursive\n>           submodule initialization from an untrusted repository or for\n>           programs which feed potentially-untrusted URLS to git commands. See\n>           git-config(1) for more details.\n>\n>       GIT_PROTOCOL\n>           For internal use only. Used in handshaking the wire protocol.\n>           Contains a colon : separated list of keys with optional values\n>           key[=value]. Presence of unknown keys and values must be ignored.\n>\n>       GIT_OPTIONAL_LOCKS\n>           If set to 0, Git will complete any requested operation without\n>           performing any optional sub-operations that require taking a lock.\n>           For example, this will prevent git status from refreshing the index\n>           as a side effect. This is useful for processes running in the\n>           background which do not want to cause lock contention with other\n>           operations on the repository. Defaults to 1.\n>\n>       GIT_REDIRECT_STDIN, GIT_REDIRECT_STDOUT, GIT_REDIRECT_STDERR\n>           Windows-only: allow redirecting the standard input/output/error\n>           handles to paths specified by the environment variables. This is\n>           particularly useful in multi-threaded applications where the\n>           canonical way to pass standard handles via CreateProcess() is not\n>           an option because it would require the handles to be marked\n>           inheritable (and consequently every spawned process would inherit\n>           them, possibly blocking regular Git operations). The primary\n>           intended use case is to use named pipes for communication (e.g.\n>           \\\\.\\pipe\\my-git-stdin-123).\n>\n>           Two special values are supported: off will simply close the\n>           corresponding standard handle, and if GIT_REDIRECT_STDERR is 2>&1,\n>           standard error will be redirected to the same handle as standard\n>           output.\n>\n>       GIT_PRINT_SHA1_ELLIPSIS (deprecated)\n>           If set to yes, print an ellipsis following an (abbreviated) SHA-1\n>           value. This affects indications of detached HEADs (git-checkout(1))\n>           and the raw diff output (git-diff(1)). Printing an ellipsis in the\n>           cases mentioned is no longer considered adequate and support for it\n>           is likely to be removed in the foreseeable future (along with the\n>           variable).\n>\n>DISCUSSION\n>       More detail on the following is available from the Git concepts chapter\n>       of the user-manual[2] and gitcore-tutorial(7).\n>\n>       A Git project normally consists of a working directory with a \".git\"\n>       subdirectory at the top level. The .git directory contains, among other\n>       things, a compressed object database representing the complete history\n>       of the project, an \"index\" file which links that history to the current\n>       contents of the working tree, and named pointers into that history such\n>       as tags and branch heads.\n>\n>       The object database contains objects of three main types: blobs, which\n>       hold file data; trees, which point to blobs and other trees to build up\n>       directory hierarchies; and commits, which each reference a single tree\n>       and some number of parent commits.\n>\n>       The commit, equivalent to what other systems call a \"changeset\" or\n>       \"version\", represents a step in the project's history, and each parent\n>       represents an immediately preceding step. Commits with more than one\n>       parent represent merges of independent lines of development.\n>\n>       All objects are named by the SHA-1 hash of their contents, normally\n>       written as a string of 40 hex digits. Such names are globally unique.\n>       The entire history leading up to a commit can be vouched for by signing\n>       just that commit. A fourth object type, the tag, is provided for this\n>       purpose.\n>\n>       When first created, objects are stored in individual files, but for\n>       efficiency may later be compressed together into \"pack files\".\n>\n>       Named pointers called refs mark interesting points in history. A ref\n>       may contain the SHA-1 name of an object or the name of another ref.\n>       Refs with names beginning ref/head/ contain the SHA-1 name of the most\n>       recent commit (or \"head\") of a branch under development. SHA-1 names of\n>       tags of interest are stored under ref/tags/. A special ref named HEAD\n>       contains the name of the currently checked-out branch.\n>\n>       The index file is initialized with a list of all paths and, for each\n>       path, a blob object and a set of attributes. The blob object represents\n>       the contents of the file as of the head of the current branch. The\n>       attributes (last modified time, size, etc.) are taken from the\n>       corresponding file in the working tree. Subsequent changes to the\n>       working tree can be found by comparing these attributes. The index may\n>       be updated with new content, and new commits may be created from the\n>       content stored in the index.\n>\n>       The index is also capable of storing multiple entries (called \"stages\")\n>       for a given pathname. These stages are used to hold the various\n>       unmerged version of a file when a merge is in progress.\n>\n>FURTHER DOCUMENTATION\n>       See the references in the \"description\" section to get started using\n>       Git. The following is probably more detail than necessary for a\n>       first-time user.\n>\n>       The Git concepts chapter of the user-manual[2] and gitcore-tutorial(7)\n>       both provide introductions to the underlying Git architecture.\n>\n>       See gitworkflows(7) for an overview of recommended workflows.\n>\n>       See also the howto[3] documents for some useful examples.\n>\n>       The internals are documented in the Git API documentation[4].\n>\n>       Users migrating from CVS may also want to read gitcvs-migration(7).\n>\n>AUTHORS\n>       Git was started by Linus Torvalds, and is currently maintained by Junio\n>       C Hamano. Numerous contributions have come from the Git mailing list\n>       <git@vger.kernel.org[5]>.\n>       http://www.openhub.net/p/git/contributors/summary gives you a more\n>       complete list of contributors.\n>\n>       If you have a clone of git.git itself, the output of git-shortlog(1)\n>       and git-blame(1) can show you the authors for specific parts of the\n>       project.\n>\n>REPORTING BUGS\n>       Report bugs to the Git mailing list <git@vger.kernel.org[5]> where the\n>       development and maintenance is primarily done. You do not have to be\n>       subscribed to the list to send a message there. See the list archive at\n>       https://public-inbox.org/git for previous bug reports and other\n>       discussions.\n>\n>       Issues which are security relevant should be disclosed privately to the\n>       Git Security mailing list <git-security@googlegroups.com[6]>.\n>\n>SEE ALSO\n>       gittutorial(7), gittutorial-2(7), giteveryday(7), gitcvs-migration(7),\n>       gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User's\n>       Manual[1], gitworkflows(7)\n>\n>GIT\n>       Part of the git(1) suite\n>\n>NOTES\n>        1. Git User's Manual\n>           file:///home/frederik/share/doc/git-doc/user-manual.html\n>\n>        2. Git concepts chapter of the user-manual\n>           file:///home/frederik/share/doc/git-doc/user-manual.html#git-concepts\n>\n>        3. howto\n>           file:///home/frederik/share/doc/git-doc/howto-index.html\n>\n>        4. Git API documentation\n>           file:///home/frederik/share/doc/git-doc/technical/api-index.html\n>\n>        5. git@vger.kernel.org\n>           mailto:git@vger.kernel.org\n>\n>        6. git-security@googlegroups.com\n>           mailto:git-security@googlegroups.com\n>\n>Git 2.21.0.rc1.9.g3f              02/18/2019                            GIT(1)\n\n"},{"id":"371152","messageId":"CA+P7+xpC5mDRx1ev-3ebGMEexgvLv-kDtM=9g35hRETOPo6c8g@mail.gmail.com","threadId":"48834","inReplyTo":"20190311090436.brdk7un7dto7rrhh@localhost","subject":"Re: [PATCH 0/1] de-alphabetize command list","fromName":"Jacob Keller","fromEmail":"jacob.keller@gmail.com","sentAt":"2019-03-11T14:38:02Z","receivedAt":"2019-03-11T14:38:20Z","isPatch":true,"sender":{"key":"jacob.keller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/874719?v=4"},"body":"On Mon, Mar 11, 2019 at 2:09 AM <frederik@ofb.net> wrote:\n>\n> Hey Git people,\n>\n> I didn't get a reply and I'm not sure what the appropriate ping\n> interval is, or when I should conclude that no one is interested.\n>\n> There seemed to be some vaguely positive feedback before I embarked on\n> this project. At the same time I don't want to pester anyone into\n> applying patches in a disorganized fashion.\n>\n> I'm not subscribed to the mailing list so I apologize if I'm out of\n> tune with a release cycle or current development thrust.\n>\n> Thanks,\n>\n> Frederick\n>\n\nFWIW, I felt like the changes in your proposed patch were good. I\nhaven't had more time to dig into reviewing it much though :(\n\n-Jake\n\n> On Thu, Feb 21, 2019 at 10:05:22AM -0800, frederik@ofb.net wrote:\n> >I realized that it would probably be easier to discuss this proposal\n> >if I attached the final command listing and the rendered manual page.\n> >Please find them attached to this message.\n> >\n> >Thank you,\n> >\n> >Frederick\n> >\n> >On Tue, Feb 19, 2019 at 09:54:12AM -0800, Frederick Eaton wrote:\n> >>This is a follow-up to my proposal to de-alphabetize the command\n> >>listings in the git(1) manual page, from 6 July 2018.\n> >>\n> >>Some projects have manual page items listed in alphabetical order,\n> >>some don't. As I argued in my proposal, I find it easier to learn from\n> >>material which is not alphabetized. If this patch is accepted, I hope\n> >>that it will make the Git documentation more accessible to myself and\n> >>others.\n> >>\n> >>I produced the reordered command list in this patch using several\n> >>sources, as indicated by comments in the new command-list.txt file.\n> >>First, all the commands in the main part of \"gittutorial(7)\" appear in\n> >>order, then the commands in giteveryday(7). Then appear additional\n> >>commands from a friend's shell history, in reverse order of frequency.\n> >>Then gittutorial-2(7), then gitcore-tutorial(7). After that there is a\n> >>list of \"guides\", followed by about 100 commands not appearing in the\n> >>earlier lists. I kept the guides and the remaining commands in their\n> >>category groupings (guide, mainporcelain, ancillarymanipulators,\n> >>etc.), but ordered the commands within each category according to my\n> >>own judgment after skimming each manual page.\n> >>\n> >>To verify that the new list is a permutation of the most recent list,\n> >>I use the following command (it should produce no output and exit 0):\n> >>\n> >>   diff <(git show master:command-list.txt | grep -v '^#' | sort ) <(cat command-list.txt | grep -v '^#' | sort)\n> >>\n> >>Note this patch changes the order of commands appearing in the\n> >>generated file \"command-list.h\", which mostly seems to be used by\n> >>\"help.c\". Probably due to the various occurrences of QSORT in\n> >>\"help.c\", I think this reordering has no visible effect. I am willing\n> >>to do any additional testing which may be recommended to ensure that\n> >>this patch has no undesired consequences.\n> >>\n> >>Frederick Eaton (1):\n> >> Prioritize list of commands appearing in git(1), via command-list.txt.\n> >>   Don't invoke 'sort' in Documentation/cmd-list.perl.\n> >>\n> >>Documentation/cmd-list.perl |   2 +-\n> >>command-list.txt            | 295 +++++++++++++++++++-----------------\n> >>2 files changed, 158 insertions(+), 139 deletions(-)\n> >>\n> >>--\n> >>2.20.1\n> >>\n>\n> ># Command classification list\n> ># ---------------------------\n> ># All supported commands, builtin or external, must be described in\n> ># here. This info is used to list commands in various places. Each\n> ># command is on one line followed by one or more attributes.\n> >#\n> ># The first attribute group is mandatory and indicates the command\n> ># type. This group includes:\n> >#\n> >#   mainporcelain\n> >#   ancillarymanipulators\n> >#   ancillaryinterrogators\n> >#   foreignscminterface\n> >#   plumbingmanipulators\n> >#   plumbinginterrogators\n> >#   synchingrepositories\n> >#   synchelpers\n> >#   purehelpers\n> >#\n> ># The type names are self explanatory. But if you want to see what\n> ># command belongs to what group to get a better picture, have a look\n> ># at \"git\" man page, \"GIT COMMANDS\" section.\n> >#\n> ># Commands of type mainporcelain can also optionally have one of these\n> ># attributes:\n> >#\n> >#   init\n> >#   worktree\n> >#   info\n> >#   history\n> >#   remote\n> >#\n> ># These commands are considered \"common\" and will show up in \"git\n> ># help\" output in groups. Uncommon porcelain commands must not\n> ># specify any of these attributes.\n> >#\n> ># \"complete\" attribute is used to mark that the command should be\n> ># completable by git-completion.bash. Note that by default,\n> ># mainporcelain commands are completable so you don't need this\n> ># attribute.\n> >#\n> ># As part of the Git man page list, the man(5/7) guides are also\n> ># specified here, which can only have \"guide\" attribute and nothing\n> ># else.\n> >#\n> ># February 2019: This list had been sorted alphabetically but has been\n> ># reordered to make it easier for people to learn from the main git(1)\n> ># manual page. The new ordering is according to approximate usefulness\n> ># / frequency of use / order of use, with some grouping by topic. The\n> ># idea is to make it possible to read the manual page from beginning\n> ># to end and see the most important commands first, rather than\n> ># getting them in alphabetical order - in other words, to make the\n> ># manual page more like a table of contents and less like an index.\n> ># Please consider this when adding new commands.\n> >#\n> >### command list (do not change this line, also do not change alignment)\n> ># command name                          category [category] [category]\n> ># From gittutorial\n> >git-help                                ancillaryinterrogators          complete\n> >git-config                              ancillarymanipulators           complete\n> >git-clone                               mainporcelain           init\n> >git-init                                mainporcelain           init\n> >git-add                                 mainporcelain           worktree\n> >git-commit                              mainporcelain           history\n> >git-diff                                mainporcelain           history\n> >git-status                              mainporcelain           info\n> >git-log                                 mainporcelain           info\n> >git-branch                              mainporcelain           history\n> >git-checkout                            mainporcelain           history\n> >git-merge                               mainporcelain           history\n> >gitk                                    mainporcelain\n> >git-pull                                mainporcelain           remote\n> >git-fetch                               mainporcelain           remote\n> ># From tutorial NEXT STEPS\n> >git-format-patch                        mainporcelain\n> >git-bisect                              mainporcelain           info\n> >giteveryday                             guide\n> >gitworkflows                            guide\n> >gitcvs-migration                        guide\n> ># From giteveryday\n> >git-reset                               mainporcelain           worktree\n> >git-rebase                              mainporcelain           history\n> >git-tag                                 mainporcelain           history\n> >git-push                                mainporcelain           remote\n> >git-send-email                          foreignscminterface             complete\n> >git-request-pull                        foreignscminterface             complete\n> >git-am                                  mainporcelain\n> >git-revert                              mainporcelain\n> >git-daemon                              synchingrepositories\n> >git-shell                               synchelpers\n> >git-http-backend                        synchingrepositories\n> >gitweb                                  ancillaryinterrogators\n> ># From user feedback\n> >git-grep                                mainporcelain           info\n> >git-show                                mainporcelain           info\n> >git-submodule                           mainporcelain\n> >git-cherry-pick                         mainporcelain\n> >git-clean                               mainporcelain\n> ># From gittutorial-2\n> >git-cat-file                            plumbinginterrogators\n> >git-ls-tree                             plumbinginterrogators\n> >git-ls-files                            plumbinginterrogators\n> >gitcore-tutorial                        guide\n> >gitglossary                             guide\n> ># From gitcore-tutorial\n> >git-update-index                        plumbingmanipulators\n> >git-diff-files                          plumbinginterrogators\n> >git-write-tree                          plumbingmanipulators\n> >git-read-tree                           plumbingmanipulators\n> >git-checkout-index                      plumbingmanipulators\n> >git-show-branch                         ancillaryinterrogators          complete\n> >git-name-rev                            plumbinginterrogators\n> >git-merge-index                         plumbingmanipulators\n> >git-repack                              ancillarymanipulators           complete\n> >git-prune-packed                        plumbingmanipulators\n> >git-update-server-info                  synchingrepositories\n> >git-prune                               ancillarymanipulators\n> >git-cherry                              plumbinginterrogators          complete\n> ># Guides, reordered\n> >gittutorial                             guide\n> >gittutorial-2                           guide\n> >gitrevisions                            guide\n> >gitignore                               guide\n> >gitcli                                  guide\n> >gitrepository-layout                    guide\n> >gitdiffcore                             guide\n> >gitmodules                              guide\n> >githooks                                guide\n> >gitnamespaces                           guide\n> >gitattributes                           guide\n> ># All other commands, sorted by man page category and then by\n> ># approximate priority\n> >git-stash                               mainporcelain\n> >git-rm                                  mainporcelain           worktree\n> >git-mv                                  mainporcelain           worktree\n> >git-gui                                 mainporcelain\n> >git-citool                              mainporcelain\n> >git-archive                             mainporcelain\n> >git-shortlog                            mainporcelain\n> >git-describe                            mainporcelain\n> >git-gc                                  mainporcelain\n> >git-notes                               mainporcelain\n> >git-worktree                            mainporcelain\n> >git-bundle                              mainporcelain\n> >git-range-diff                          mainporcelain\n> >git-stage                                                               complete\n> >git-reflog                              ancillarymanipulators           complete\n> >git-remote                              ancillarymanipulators           complete\n> >git-mergetool                           ancillarymanipulators           complete\n> >git-filter-branch                       ancillarymanipulators\n> >git-replace                             ancillarymanipulators           complete\n> >git-fast-export                         ancillarymanipulators\n> >git-fast-import                         ancillarymanipulators\n> >git-pack-refs                           ancillarymanipulators\n> >git-cvsimport                           foreignscminterface\n> >git-cvsserver                           foreignscminterface\n> >git-cvsexportcommit                     foreignscminterface\n> >git-svn                                 foreignscminterface\n> >git-p4                                  foreignscminterface\n> >git-quiltimport                         foreignscminterface\n> >git-archimport                          foreignscminterface\n> >git-imap-send                           foreignscminterface\n> >git-apply                               plumbingmanipulators            complete\n> >git-merge-file                          plumbingmanipulators\n> >git-mktag                               plumbingmanipulators\n> >git-hash-object                         plumbingmanipulators\n> >git-update-ref                          plumbingmanipulators\n> >git-symbolic-ref                        plumbingmanipulators\n> >git-commit-tree                         plumbingmanipulators\n> >git-commit-graph                        plumbingmanipulators\n> >git-mktree                              plumbingmanipulators\n> >git-pack-objects                        plumbingmanipulators\n> >git-unpack-objects                      plumbingmanipulators\n> >git-index-pack                          plumbingmanipulators\n> >git-multi-pack-index                    plumbingmanipulators\n> >git-blame                               ancillaryinterrogators          complete\n> >git-annotate                            ancillaryinterrogators\n> >git-instaweb                            ancillaryinterrogators          complete\n> >git-rerere                              ancillaryinterrogators\n> >git-fsck                                ancillaryinterrogators          complete\n> >git-whatchanged                         ancillaryinterrogators          complete\n> >git-difftool                            ancillaryinterrogators          complete\n> >git-merge-tree                          ancillaryinterrogators\n> >git-count-objects                       ancillaryinterrogators\n> >git-verify-commit                       ancillaryinterrogators\n> >git-verify-tag                          ancillaryinterrogators\n> >git-send-pack                           synchingrepositories\n> >git-fetch-pack                          synchingrepositories\n> >git-parse-remote                        synchelpers\n> >git-receive-pack                        synchelpers\n> >git-upload-pack                         synchelpers\n> >git-upload-archive                      synchelpers\n> >git-http-fetch                          synchelpers\n> >git-http-push                           synchelpers\n> >git-var                                 plumbinginterrogators\n> >git-rev-list                            plumbinginterrogators\n> >git-rev-parse                           plumbinginterrogators\n> >git-for-each-ref                        plumbinginterrogators\n> >git-show-ref                            plumbinginterrogators\n> >git-ls-remote                           plumbinginterrogators\n> >git-diff-tree                           plumbinginterrogators\n> >git-diff-index                          plumbinginterrogators\n> >git-merge-base                          plumbinginterrogators\n> >git-verify-pack                         plumbinginterrogators\n> >git-pack-redundant                      plumbinginterrogators\n> >git-unpack-file                         plumbinginterrogators\n> >git-show-index                          plumbinginterrogators\n> >git-get-tar-commit-id                   plumbinginterrogators\n> >git-merge-one-file                      purehelpers\n> >git-sh-setup                            purehelpers\n> >git-check-ref-format                    purehelpers\n> >git-check-ignore                        purehelpers\n> >git-check-attr                          purehelpers\n> >git-credential                          purehelpers\n> >git-credential-cache                    purehelpers\n> >git-credential-store                    purehelpers\n> >git-fmt-merge-msg                       purehelpers\n> >git-check-mailmap                       purehelpers\n> >git-mailsplit                           purehelpers\n> >git-mailinfo                            purehelpers\n> >git-interpret-trailers                  purehelpers\n> >git-column                              purehelpers\n> >git-stripspace                          purehelpers\n> >git-patch-id                            purehelpers\n> >git-sh-i18n                             purehelpers\n>\n> >GIT(1)                            Git Manual                            GIT(1)\n> >\n> >NAME\n> >       git - the stupid content tracker\n> >\n> >SYNOPSIS\n> >       git [--version] [--help] [-C <path>] [-c <name>=<value>]\n> >           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]\n> >           [-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]\n> >           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]\n> >           [--super-prefix=<path>]\n> >           <command> [<args>]\n> >\n> >DESCRIPTION\n> >       Git is a fast, scalable, distributed revision control system with an\n> >       unusually rich command set that provides both high-level operations and\n> >       full access to internals.\n> >\n> >       See gittutorial(7) to get started, then see giteveryday(7) for a useful\n> >       minimum set of commands. The Git User's Manual[1] has a more in-depth\n> >       introduction.\n> >\n> >       After you mastered the basic concepts, you can come back to this page\n> >       to learn what commands Git offers. You can learn more about individual\n> >       Git commands with \"git help command\". gitcli(7) manual page gives you\n> >       an overview of the command-line command syntax.\n> >\n> >       A formatted and hyperlinked copy of the latest Git documentation can be\n> >       viewed at https://git.github.io/htmldocs/git.html.\n> >\n> >OPTIONS\n> >       --version\n> >           Prints the Git suite version that the git program came from.\n> >\n> >       --help\n> >           Prints the synopsis and a list of the most commonly used commands.\n> >           If the option --all or -a is given then all available commands are\n> >           printed. If a Git command is named this option will bring up the\n> >           manual page for that command.\n> >\n> >           Other options are available to control how the manual page is\n> >           displayed. See git-help(1) for more information, because git --help\n> >           ...  is converted internally into git help ....\n> >\n> >       -C <path>\n> >           Run as if git was started in <path> instead of the current working\n> >           directory. When multiple -C options are given, each subsequent\n> >           non-absolute -C <path> is interpreted relative to the preceding -C\n> >           <path>.\n> >\n> >           This option affects options that expect path name like --git-dir\n> >           and --work-tree in that their interpretations of the path names\n> >           would be made relative to the working directory caused by the -C\n> >           option. For example the following invocations are equivalent:\n> >\n> >               git --git-dir=a.git --work-tree=b -C c status\n> >               git --git-dir=c/a.git --work-tree=c/b status\n> >\n> >       -c <name>=<value>\n> >           Pass a configuration parameter to the command. The value given will\n> >           override values from configuration files. The <name> is expected in\n> >           the same format as listed by git config (subkeys separated by\n> >           dots).\n> >\n> >           Note that omitting the = in git -c foo.bar ...  is allowed and sets\n> >           foo.bar to the boolean true value (just like [foo]bar would in a\n> >           config file). Including the equals but with an empty value (like\n> >           git -c foo.bar= ...) sets foo.bar to the empty string which git\n> >           config --type=bool will convert to false.\n> >\n> >       --exec-path[=<path>]\n> >           Path to wherever your core Git programs are installed. This can\n> >           also be controlled by setting the GIT_EXEC_PATH environment\n> >           variable. If no path is given, git will print the current setting\n> >           and then exit.\n> >\n> >       --html-path\n> >           Print the path, without trailing slash, where Git's HTML\n> >           documentation is installed and exit.\n> >\n> >       --man-path\n> >           Print the manpath (see man(1)) for the man pages for this version\n> >           of Git and exit.\n> >\n> >       --info-path\n> >           Print the path where the Info files documenting this version of Git\n> >           are installed and exit.\n> >\n> >       -p, --paginate\n> >           Pipe all output into less (or if set, $PAGER) if standard output is\n> >           a terminal. This overrides the pager.<cmd> configuration options\n> >           (see the \"Configuration Mechanism\" section below).\n> >\n> >       -P, --no-pager\n> >           Do not pipe Git output into a pager.\n> >\n> >       --git-dir=<path>\n> >           Set the path to the repository. This can also be controlled by\n> >           setting the GIT_DIR environment variable. It can be an absolute\n> >           path or relative path to current working directory.\n> >\n> >       --work-tree=<path>\n> >           Set the path to the working tree. It can be an absolute path or a\n> >           path relative to the current working directory. This can also be\n> >           controlled by setting the GIT_WORK_TREE environment variable and\n> >           the core.worktree configuration variable (see core.worktree in git-\n> >           config(1) for a more detailed discussion).\n> >\n> >       --namespace=<path>\n> >           Set the Git namespace. See gitnamespaces(7) for more details.\n> >           Equivalent to setting the GIT_NAMESPACE environment variable.\n> >\n> >       --super-prefix=<path>\n> >           Currently for internal use only. Set a prefix which gives a path\n> >           from above a repository down to its root. One use is to give\n> >           submodules context about the superproject that invoked it.\n> >\n> >       --bare\n> >           Treat the repository as a bare repository. If GIT_DIR environment\n> >           is not set, it is set to the current working directory.\n> >\n> >       --no-replace-objects\n> >           Do not use replacement refs to replace Git objects. See git-\n> >           replace(1) for more information.\n> >\n> >       --literal-pathspecs\n> >           Treat pathspecs literally (i.e. no globbing, no pathspec magic).\n> >           This is equivalent to setting the GIT_LITERAL_PATHSPECS environment\n> >           variable to 1.\n> >\n> >       --glob-pathspecs\n> >           Add \"glob\" magic to all pathspec. This is equivalent to setting the\n> >           GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on\n> >           individual pathspecs can be done using pathspec magic \":(literal)\"\n> >\n> >       --noglob-pathspecs\n> >           Add \"literal\" magic to all pathspec. This is equivalent to setting\n> >           the GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling\n> >           globbing on individual pathspecs can be done using pathspec magic\n> >           \":(glob)\"\n> >\n> >       --icase-pathspecs\n> >           Add \"icase\" magic to all pathspec. This is equivalent to setting\n> >           the GIT_ICASE_PATHSPECS environment variable to 1.\n> >\n> >       --no-optional-locks\n> >           Do not perform optional operations that require locks. This is\n> >           equivalent to setting the GIT_OPTIONAL_LOCKS to 0.\n> >\n> >       --list-cmds=group[,group...]\n> >           List commands by group. This is an internal/experimental option and\n> >           may change or be removed in the future. Supported groups are:\n> >           builtins, parseopt (builtin commands that use parse-options), main\n> >           (all commands in libexec directory), others (all other commands in\n> >           $PATH that have git- prefix), list-<category> (see categories in\n> >           command-list.txt), nohelpers (exclude helper commands), alias and\n> >           config (retrieve command list from config variable\n> >           completion.commands)\n> >\n> >GIT COMMANDS\n> >       We divide Git into high level (\"porcelain\") commands and low level\n> >       (\"plumbing\") commands.\n> >\n> >HIGH-LEVEL COMMANDS (PORCELAIN)\n> >       We separate the porcelain commands into the main commands and some\n> >       ancillary user utilities.\n> >\n> >   Main porcelain commands\n> >       git-clone(1)\n> >           Clone a repository into a new directory.\n> >\n> >       git-init(1)\n> >           Create an empty Git repository or reinitialize an existing one.\n> >\n> >       git-add(1)\n> >           Add file contents to the index.\n> >\n> >       git-commit(1)\n> >           Record changes to the repository.\n> >\n> >       git-diff(1)\n> >           Show changes between commits, commit and working tree, etc.\n> >\n> >       git-status(1)\n> >           Show the working tree status.\n> >\n> >       git-log(1)\n> >           Show commit logs.\n> >\n> >       git-branch(1)\n> >           List, create, or delete branches.\n> >\n> >       git-checkout(1)\n> >           Switch branches or restore working tree files.\n> >\n> >       git-merge(1)\n> >           Join two or more development histories together.\n> >\n> >       gitk(1)\n> >           The Git repository browser.\n> >\n> >       git-pull(1)\n> >           Fetch from and integrate with another repository or a local branch.\n> >\n> >       git-fetch(1)\n> >           Download objects and refs from another repository.\n> >\n> >       git-format-patch(1)\n> >           Prepare patches for e-mail submission.\n> >\n> >       git-bisect(1)\n> >           Use binary search to find the commit that introduced a bug.\n> >\n> >       git-reset(1)\n> >           Reset current HEAD to the specified state.\n> >\n> >       git-rebase(1)\n> >           Reapply commits on top of another base tip.\n> >\n> >       git-tag(1)\n> >           Create, list, delete or verify a tag object signed with GPG.\n> >\n> >       git-push(1)\n> >           Update remote refs along with associated objects.\n> >\n> >       git-am(1)\n> >           Apply a series of patches from a mailbox.\n> >\n> >       git-revert(1)\n> >           Revert some existing commits.\n> >\n> >       git-grep(1)\n> >           Print lines matching a pattern.\n> >\n> >       git-show(1)\n> >           Show various types of objects.\n> >\n> >       git-submodule(1)\n> >           Initialize, update or inspect submodules.\n> >\n> >       git-cherry-pick(1)\n> >           Apply the changes introduced by some existing commits.\n> >\n> >       git-clean(1)\n> >           Remove untracked files from the working tree.\n> >\n> >       git-stash(1)\n> >           Stash the changes in a dirty working directory away.\n> >\n> >       git-rm(1)\n> >           Remove files from the working tree and from the index.\n> >\n> >       git-mv(1)\n> >           Move or rename a file, a directory, or a symlink.\n> >\n> >       git-gui(1)\n> >           A portable graphical interface to Git.\n> >\n> >       git-citool(1)\n> >           Graphical alternative to git-commit.\n> >\n> >       git-archive(1)\n> >           Create an archive of files from a named tree.\n> >\n> >       git-shortlog(1)\n> >           Summarize git log output.\n> >\n> >       git-describe(1)\n> >           Give an object a human readable name based on an available ref.\n> >\n> >       git-gc(1)\n> >           Cleanup unnecessary files and optimize the local repository.\n> >\n> >       git-notes(1)\n> >           Add or inspect object notes.\n> >\n> >       git-worktree(1)\n> >           Manage multiple working trees.\n> >\n> >       git-bundle(1)\n> >           Move objects and refs by archive.\n> >\n> >       git-range-diff(1)\n> >           Compare two commit ranges (e.g. two versions of a branch).\n> >\n> >   Ancillary Commands\n> >       Manipulators:\n> >\n> >       git-config(1)\n> >           Get and set repository or global options.\n> >\n> >       git-repack(1)\n> >           Pack unpacked objects in a repository.\n> >\n> >       git-prune(1)\n> >           Prune all unreachable objects from the object database.\n> >\n> >       git-reflog(1)\n> >           Manage reflog information.\n> >\n> >       git-remote(1)\n> >           Manage set of tracked repositories.\n> >\n> >       git-mergetool(1)\n> >           Run merge conflict resolution tools to resolve merge conflicts.\n> >\n> >       git-filter-branch(1)\n> >           Rewrite branches.\n> >\n> >       git-replace(1)\n> >           Create, list, delete refs to replace objects.\n> >\n> >       git-fast-export(1)\n> >           Git data exporter.\n> >\n> >       git-fast-import(1)\n> >           Backend for fast Git data importers.\n> >\n> >       git-pack-refs(1)\n> >           Pack heads and tags for efficient repository access.\n> >\n> >       Interrogators:\n> >\n> >       git-help(1)\n> >           Display help information about Git.\n> >\n> >       gitweb(1)\n> >           Git web interface (web frontend to Git repositories).\n> >\n> >       git-show-branch(1)\n> >           Show branches and their commits.\n> >\n> >       git-blame(1)\n> >           Show what revision and author last modified each line of a file.\n> >\n> >       git-annotate(1)\n> >           Annotate file lines with commit information.\n> >\n> >       git-instaweb(1)\n> >           Instantly browse your working repository in gitweb.\n> >\n> >       git-rerere(1)\n> >           Reuse recorded resolution of conflicted merges.\n> >\n> >       git-fsck(1)\n> >           Verifies the connectivity and validity of the objects in the\n> >           database.\n> >\n> >       git-whatchanged(1)\n> >           Show logs with difference each commit introduces.\n> >\n> >       git-difftool(1)\n> >           Show changes using common diff tools.\n> >\n> >       git-merge-tree(1)\n> >           Show three-way merge without touching index.\n> >\n> >       git-count-objects(1)\n> >           Count unpacked number of objects and their disk consumption.\n> >\n> >       git-verify-commit(1)\n> >           Check the GPG signature of commits.\n> >\n> >       git-verify-tag(1)\n> >           Check the GPG signature of tags.\n> >\n> >   Interacting with Others\n> >       These commands are to interact with foreign SCM and with other people\n> >       via patch over e-mail.\n> >\n> >       git-send-email(1)\n> >           Send a collection of patches as emails.\n> >\n> >       git-request-pull(1)\n> >           Generates a summary of pending changes.\n> >\n> >       git-cvsimport(1)\n> >           Salvage your data out of another SCM people love to hate.\n> >\n> >       git-cvsserver(1)\n> >           A CVS server emulator for Git.\n> >\n> >       git-cvsexportcommit(1)\n> >           Export a single commit to a CVS checkout.\n> >\n> >       git-svn(1)\n> >           Bidirectional operation between a Subversion repository and Git.\n> >\n> >       git-p4(1)\n> >           Import from and submit to Perforce repositories.\n> >\n> >       git-quiltimport(1)\n> >           Applies a quilt patchset onto the current branch.\n> >\n> >       git-archimport(1)\n> >           Import a GNU Arch repository into Git.\n> >\n> >       git-imap-send(1)\n> >           Send a collection of patches from stdin to an IMAP folder.\n> >\n> >LOW-LEVEL COMMANDS (PLUMBING)\n> >       Although Git includes its own porcelain layer, its low-level commands\n> >       are sufficient to support development of alternative porcelains.\n> >       Developers of such porcelains might start by reading about git-update-\n> >       index(1) and git-read-tree(1).\n> >\n> >       The interface (input, output, set of options and the semantics) to\n> >       these low-level commands are meant to be a lot more stable than\n> >       Porcelain level commands, because these commands are primarily for\n> >       scripted use. The interface to Porcelain commands on the other hand are\n> >       subject to change in order to improve the end user experience.\n> >\n> >       The following description divides the low-level commands into commands\n> >       that manipulate objects (in the repository, index, and working tree),\n> >       commands that interrogate and compare objects, and commands that move\n> >       objects and references between repositories.\n> >\n> >   Manipulation commands\n> >       git-update-index(1)\n> >           Register file contents in the working tree to the index.\n> >\n> >       git-write-tree(1)\n> >           Create a tree object from the current index.\n> >\n> >       git-read-tree(1)\n> >           Reads tree information into the index.\n> >\n> >       git-checkout-index(1)\n> >           Copy files from the index to the working tree.\n> >\n> >       git-merge-index(1)\n> >           Run a merge for files needing merging.\n> >\n> >       git-prune-packed(1)\n> >           Remove extra objects that are already in pack files.\n> >\n> >       git-apply(1)\n> >           Apply a patch to files and/or to the index.\n> >\n> >       git-merge-file(1)\n> >           Run a three-way file merge.\n> >\n> >       git-mktag(1)\n> >           Creates a tag object.\n> >\n> >       git-hash-object(1)\n> >           Compute object ID and optionally creates a blob from a file.\n> >\n> >       git-update-ref(1)\n> >           Update the object name stored in a ref safely.\n> >\n> >       git-symbolic-ref(1)\n> >           Read, modify and delete symbolic refs.\n> >\n> >       git-commit-tree(1)\n> >           Create a new commit object.\n> >\n> >       git-commit-graph(1)\n> >           Write and verify Git commit-graph files.\n> >\n> >       git-mktree(1)\n> >           Build a tree-object from ls-tree formatted text.\n> >\n> >       git-pack-objects(1)\n> >           Create a packed archive of objects.\n> >\n> >       git-unpack-objects(1)\n> >           Unpack objects from a packed archive.\n> >\n> >       git-index-pack(1)\n> >           Build pack index file for an existing packed archive.\n> >\n> >       git-multi-pack-index(1)\n> >           Write and verify multi-pack-indexes.\n> >\n> >   Interrogation commands\n> >       git-cat-file(1)\n> >           Provide content or type and size information for repository\n> >           objects.\n> >\n> >       git-ls-tree(1)\n> >           List the contents of a tree object.\n> >\n> >       git-ls-files(1)\n> >           Show information about files in the index and the working tree.\n> >\n> >       git-diff-files(1)\n> >           Compares files in the working tree and the index.\n> >\n> >       git-name-rev(1)\n> >           Find symbolic names for given revs.\n> >\n> >       git-cherry(1)\n> >           Find commits yet to be applied to upstream.\n> >\n> >       git-var(1)\n> >           Show a Git logical variable.\n> >\n> >       git-rev-list(1)\n> >           Lists commit objects in reverse chronological order.\n> >\n> >       git-rev-parse(1)\n> >           Pick out and massage parameters.\n> >\n> >       git-for-each-ref(1)\n> >           Output information on each ref.\n> >\n> >       git-show-ref(1)\n> >           List references in a local repository.\n> >\n> >       git-ls-remote(1)\n> >           List references in a remote repository.\n> >\n> >       git-diff-tree(1)\n> >           Compares the content and mode of blobs found via two tree objects.\n> >\n> >       git-diff-index(1)\n> >           Compare a tree to the working tree or index.\n> >\n> >       git-merge-base(1)\n> >           Find as good common ancestors as possible for a merge.\n> >\n> >       git-verify-pack(1)\n> >           Validate packed Git archive files.\n> >\n> >       git-pack-redundant(1)\n> >           Find redundant pack files.\n> >\n> >       git-unpack-file(1)\n> >           Creates a temporary file with a blob's contents.\n> >\n> >       git-show-index(1)\n> >           Show packed archive index.\n> >\n> >       git-get-tar-commit-id(1)\n> >           Extract commit ID from an archive created using git-archive.\n> >\n> >       In general, the interrogate commands do not touch the files in the\n> >       working tree.\n> >\n> >   Synching repositories\n> >       git-daemon(1)\n> >           A really simple server for Git repositories.\n> >\n> >       git-http-backend(1)\n> >           Server side implementation of Git over HTTP.\n> >\n> >       git-update-server-info(1)\n> >           Update auxiliary info file to help dumb servers.\n> >\n> >       git-send-pack(1)\n> >           Push objects over Git protocol to another repository.\n> >\n> >       git-fetch-pack(1)\n> >           Receive missing objects from another repository.\n> >\n> >       The following are helper commands used by the above; end users\n> >       typically do not use them directly.\n> >\n> >       git-shell(1)\n> >           Restricted login shell for Git-only SSH access.\n> >\n> >       git-parse-remote(1)\n> >           Routines to help parsing remote repository access parameters.\n> >\n> >       git-receive-pack(1)\n> >           Receive what is pushed into the repository.\n> >\n> >       git-upload-pack(1)\n> >           Send objects packed back to git-fetch-pack.\n> >\n> >       git-upload-archive(1)\n> >           Send archive back to git-archive.\n> >\n> >       git-http-fetch(1)\n> >           Download from a remote Git repository via HTTP.\n> >\n> >       git-http-push(1)\n> >           Push objects over HTTP/DAV to another repository.\n> >\n> >   Internal helper commands\n> >       These are internal helper commands used by other commands; end users\n> >       typically do not use them directly.\n> >\n> >       git-merge-one-file(1)\n> >           The standard helper program to use with git-merge-index.\n> >\n> >       git-sh-setup(1)\n> >           Common Git shell script setup code.\n> >\n> >       git-check-ref-format(1)\n> >           Ensures that a reference name is well formed.\n> >\n> >       git-check-ignore(1)\n> >           Debug gitignore / exclude files.\n> >\n> >       git-check-attr(1)\n> >           Display gitattributes information.\n> >\n> >       git-credential(1)\n> >           Retrieve and store user credentials.\n> >\n> >       git-credential-cache(1)\n> >           Helper to temporarily store passwords in memory.\n> >\n> >       git-credential-store(1)\n> >           Helper to store credentials on disk.\n> >\n> >       git-fmt-merge-msg(1)\n> >           Produce a merge commit message.\n> >\n> >       git-check-mailmap(1)\n> >           Show canonical names and email addresses of contacts.\n> >\n> >       git-mailsplit(1)\n> >           Simple UNIX mbox splitter program.\n> >\n> >       git-mailinfo(1)\n> >           Extracts patch and authorship from a single e-mail message.\n> >\n> >       git-interpret-trailers(1)\n> >           add or parse structured information in commit messages.\n> >\n> >       git-column(1)\n> >           Display data in columns.\n> >\n> >       git-stripspace(1)\n> >           Remove unnecessary whitespace.\n> >\n> >       git-patch-id(1)\n> >           Compute unique ID for a patch.\n> >\n> >       git-sh-i18n(1)\n> >           Git's i18n setup code for shell scripts.\n> >\n> >CONFIGURATION MECHANISM\n> >       Git uses a simple text format to store customizations that are per\n> >       repository and are per user. Such a configuration file may look like\n> >       this:\n> >\n> >           #\n> >           # A '#' or ';' character indicates a comment.\n> >           #\n> >\n> >           ; core variables\n> >           [core]\n> >                   ; Don't trust file modes\n> >                   filemode = false\n> >\n> >           ; user identity\n> >           [user]\n> >                   name = \"Junio C Hamano\"\n> >                   email = \"gitster@pobox.com\"\n> >\n> >       Various commands read from the configuration file and adjust their\n> >       operation accordingly. See git-config(1) for a list and more details\n> >       about the configuration mechanism.\n> >\n> >IDENTIFIER TERMINOLOGY\n> >       <object>\n> >           Indicates the object name for any type of object.\n> >\n> >       <blob>\n> >           Indicates a blob object name.\n> >\n> >       <tree>\n> >           Indicates a tree object name.\n> >\n> >       <commit>\n> >           Indicates a commit object name.\n> >\n> >       <tree-ish>\n> >           Indicates a tree, commit or tag object name. A command that takes a\n> >           <tree-ish> argument ultimately wants to operate on a <tree> object\n> >           but automatically dereferences <commit> and <tag> objects that\n> >           point at a <tree>.\n> >\n> >       <commit-ish>\n> >           Indicates a commit or tag object name. A command that takes a\n> >           <commit-ish> argument ultimately wants to operate on a <commit>\n> >           object but automatically dereferences <tag> objects that point at a\n> >           <commit>.\n> >\n> >       <type>\n> >           Indicates that an object type is required. Currently one of: blob,\n> >           tree, commit, or tag.\n> >\n> >       <file>\n> >           Indicates a filename - almost always relative to the root of the\n> >           tree structure GIT_INDEX_FILE describes.\n> >\n> >SYMBOLIC IDENTIFIERS\n> >       Any Git command accepting any <object> can also use the following\n> >       symbolic notation:\n> >\n> >       HEAD\n> >           indicates the head of the current branch.\n> >\n> >       <tag>\n> >           a valid tag name (i.e. a refs/tags/<tag> reference).\n> >\n> >       <head>\n> >           a valid head name (i.e. a refs/heads/<head> reference).\n> >\n> >       For a more complete list of ways to spell object names, see \"SPECIFYING\n> >       REVISIONS\" section in gitrevisions(7).\n> >\n> >FILE/DIRECTORY STRUCTURE\n> >       Please see the gitrepository-layout(5) document.\n> >\n> >       Read githooks(5) for more details about each hook.\n> >\n> >       Higher level SCMs may provide and manage additional information in the\n> >       $GIT_DIR.\n> >\n> >TERMINOLOGY\n> >       Please see gitglossary(7).\n> >\n> >ENVIRONMENT VARIABLES\n> >       Various Git commands use the following environment variables:\n> >\n> >   The Git Repository\n> >       These environment variables apply to all core Git commands. Nb: it is\n> >       worth noting that they may be used/overridden by SCMS sitting above Git\n> >       so take care if using a foreign front-end.\n> >\n> >       GIT_INDEX_FILE\n> >           This environment allows the specification of an alternate index\n> >           file. If not specified, the default of $GIT_DIR/index is used.\n> >\n> >       GIT_INDEX_VERSION\n> >           This environment variable allows the specification of an index\n> >           version for new repositories. It won't affect existing index files.\n> >           By default index file version 2 or 3 is used. See git-update-\n> >           index(1) for more information.\n> >\n> >       GIT_OBJECT_DIRECTORY\n> >           If the object storage directory is specified via this environment\n> >           variable then the sha1 directories are created underneath -\n> >           otherwise the default $GIT_DIR/objects directory is used.\n> >\n> >       GIT_ALTERNATE_OBJECT_DIRECTORIES\n> >           Due to the immutable nature of Git objects, old objects can be\n> >           archived into shared, read-only directories. This variable\n> >           specifies a \":\" separated (on Windows \";\" separated) list of Git\n> >           object directories which can be used to search for Git objects. New\n> >           objects will not be written to these directories.\n> >\n> >           Entries that begin with \" (double-quote) will be interpreted as\n> >           C-style quoted paths, removing leading and trailing double-quotes\n> >           and respecting backslash escapes. E.g., the value\n> >           \"path-with-\\\"-and-:-in-it\":vanilla-path has two paths:\n> >           path-with-\"-and-:-in-it and vanilla-path.\n> >\n> >       GIT_DIR\n> >           If the GIT_DIR environment variable is set then it specifies a path\n> >           to use instead of the default .git for the base of the repository.\n> >           The --git-dir command-line option also sets this value.\n> >\n> >       GIT_WORK_TREE\n> >           Set the path to the root of the working tree. This can also be\n> >           controlled by the --work-tree command-line option and the\n> >           core.worktree configuration variable.\n> >\n> >       GIT_NAMESPACE\n> >           Set the Git namespace; see gitnamespaces(7) for details. The\n> >           --namespace command-line option also sets this value.\n> >\n> >       GIT_CEILING_DIRECTORIES\n> >           This should be a colon-separated list of absolute paths. If set, it\n> >           is a list of directories that Git should not chdir up into while\n> >           looking for a repository directory (useful for excluding\n> >           slow-loading network directories). It will not exclude the current\n> >           working directory or a GIT_DIR set on the command line or in the\n> >           environment. Normally, Git has to read the entries in this list and\n> >           resolve any symlink that might be present in order to compare them\n> >           with the current directory. However, if even this access is slow,\n> >           you can add an empty entry to the list to tell Git that the\n> >           subsequent entries are not symlinks and needn't be resolved; e.g.,\n> >           GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink.\n> >\n> >       GIT_DISCOVERY_ACROSS_FILESYSTEM\n> >           When run in a directory that does not have \".git\" repository\n> >           directory, Git tries to find such a directory in the parent\n> >           directories to find the top of the working tree, but by default it\n> >           does not cross filesystem boundaries. This environment variable can\n> >           be set to true to tell Git not to stop at filesystem boundaries.\n> >           Like GIT_CEILING_DIRECTORIES, this will not affect an explicit\n> >           repository directory set via GIT_DIR or on the command line.\n> >\n> >       GIT_COMMON_DIR\n> >           If this variable is set to a path, non-worktree files that are\n> >           normally in $GIT_DIR will be taken from this path instead.\n> >           Worktree-specific files such as HEAD or index are taken from\n> >           $GIT_DIR. See gitrepository-layout(5) and git-worktree(1) for\n> >           details. This variable has lower precedence than other path\n> >           variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...\n> >\n> >   Git Commits\n> >       GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_AUTHOR_DATE, GIT_COMMITTER_NAME,\n> >       GIT_COMMITTER_EMAIL, GIT_COMMITTER_DATE, EMAIL\n> >           see git-commit-tree(1)\n> >\n> >   Git Diffs\n> >       GIT_DIFF_OPTS\n> >           Only valid setting is \"--unified=??\" or \"-u??\" to set the number of\n> >           context lines shown when a unified diff is created. This takes\n> >           precedence over any \"-U\" or \"--unified\" option value passed on the\n> >           Git diff command line.\n> >\n> >       GIT_EXTERNAL_DIFF\n> >           When the environment variable GIT_EXTERNAL_DIFF is set, the program\n> >           named by it is called, instead of the diff invocation described\n> >           above. For a path that is added, removed, or modified,\n> >           GIT_EXTERNAL_DIFF is called with 7 parameters:\n> >\n> >               path old-file old-hex old-mode new-file new-hex new-mode\n> >\n> >           where:\n> >\n> >       <old|new>-file\n> >           are files GIT_EXTERNAL_DIFF can use to read the contents of\n> >           <old|new>,\n> >\n> >       <old|new>-hex\n> >           are the 40-hexdigit SHA-1 hashes,\n> >\n> >       <old|new>-mode\n> >           are the octal representation of the file modes.\n> >\n> >           The file parameters can point at the user's working file (e.g.\n> >           new-file in \"git-diff-files\"), /dev/null (e.g.  old-file when a new\n> >           file is added), or a temporary file (e.g.  old-file in the index).\n> >           GIT_EXTERNAL_DIFF should not worry about unlinking the temporary\n> >           file --- it is removed when GIT_EXTERNAL_DIFF exits.\n> >\n> >           For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1\n> >           parameter, <path>.\n> >\n> >           For each path GIT_EXTERNAL_DIFF is called, two environment\n> >           variables, GIT_DIFF_PATH_COUNTER and GIT_DIFF_PATH_TOTAL are set.\n> >\n> >       GIT_DIFF_PATH_COUNTER\n> >           A 1-based counter incremented by one for every path.\n> >\n> >       GIT_DIFF_PATH_TOTAL\n> >           The total number of paths.\n> >\n> >   other\n> >       GIT_MERGE_VERBOSITY\n> >           A number controlling the amount of output shown by the recursive\n> >           merge strategy. Overrides merge.verbosity. See git-merge(1)\n> >\n> >       GIT_PAGER\n> >           This environment variable overrides $PAGER. If it is set to an\n> >           empty string or to the value \"cat\", Git will not launch a pager.\n> >           See also the core.pager option in git-config(1).\n> >\n> >       GIT_EDITOR\n> >           This environment variable overrides $EDITOR and $VISUAL. It is used\n> >           by several Git commands when, on interactive mode, an editor is to\n> >           be launched. See also git-var(1) and the core.editor option in git-\n> >           config(1).\n> >\n> >       GIT_SSH, GIT_SSH_COMMAND\n> >           If either of these environment variables is set then git fetch and\n> >           git push will use the specified command instead of ssh when they\n> >           need to connect to a remote system. The command-line parameters\n> >           passed to the configured command are determined by the ssh variant.\n> >           See ssh.variant option in git-config(1) for details.\n> >\n> >       + $GIT_SSH_COMMAND takes precedence over $GIT_SSH, and is interpreted\n> >       by the shell, which allows additional arguments to be included.\n> >       $GIT_SSH on the other hand must be just the path to a program (which\n> >       can be a wrapper shell script, if additional arguments are needed).\n> >\n> >       + Usually it is easier to configure any desired options through your\n> >       personal .ssh/config file. Please consult your ssh documentation for\n> >       further details.\n> >\n> >       GIT_SSH_VARIANT\n> >           If this environment variable is set, it overrides Git's\n> >           autodetection whether GIT_SSH/GIT_SSH_COMMAND/core.sshCommand refer\n> >           to OpenSSH, plink or tortoiseplink. This variable overrides the\n> >           config setting ssh.variant that serves the same purpose.\n> >\n> >       GIT_ASKPASS\n> >           If this environment variable is set, then Git commands which need\n> >           to acquire passwords or passphrases (e.g. for HTTP or IMAP\n> >           authentication) will call this program with a suitable prompt as\n> >           command-line argument and read the password from its STDOUT. See\n> >           also the core.askPass option in git-config(1).\n> >\n> >       GIT_TERMINAL_PROMPT\n> >           If this environment variable is set to 0, git will not prompt on\n> >           the terminal (e.g., when asking for HTTP authentication).\n> >\n> >       GIT_CONFIG_NOSYSTEM\n> >           Whether to skip reading settings from the system-wide\n> >           $(prefix)/etc/gitconfig file. This environment variable can be used\n> >           along with $HOME and $XDG_CONFIG_HOME to create a predictable\n> >           environment for a picky script, or you can set it temporarily to\n> >           avoid using a buggy /etc/gitconfig file while waiting for someone\n> >           with sufficient permissions to fix it.\n> >\n> >       GIT_FLUSH\n> >           If this environment variable is set to \"1\", then commands such as\n> >           git blame (in incremental mode), git rev-list, git log, git\n> >           check-attr and git check-ignore will force a flush of the output\n> >           stream after each record have been flushed. If this variable is set\n> >           to \"0\", the output of these commands will be done using completely\n> >           buffered I/O. If this environment variable is not set, Git will\n> >           choose buffered or record-oriented flushing based on whether stdout\n> >           appears to be redirected to a file or not.\n> >\n> >       GIT_TRACE\n> >           Enables general trace messages, e.g. alias expansion, built-in\n> >           command execution and external command execution.\n> >\n> >           If this variable is set to \"1\", \"2\" or \"true\" (comparison is case\n> >           insensitive), trace messages will be printed to stderr.\n> >\n> >           If the variable is set to an integer value greater than 2 and lower\n> >           than 10 (strictly) then Git will interpret this value as an open\n> >           file descriptor and will try to write the trace messages into this\n> >           file descriptor.\n> >\n> >           Alternatively, if the variable is set to an absolute path (starting\n> >           with a / character), Git will interpret this as a file path and\n> >           will try to append the trace messages to it.\n> >\n> >           Unsetting the variable, or setting it to empty, \"0\" or \"false\"\n> >           (case insensitive) disables trace messages.\n> >\n> >       GIT_TRACE_FSMONITOR\n> >           Enables trace messages for the filesystem monitor extension. See\n> >           GIT_TRACE for available trace output options.\n> >\n> >       GIT_TRACE_PACK_ACCESS\n> >           Enables trace messages for all accesses to any packs. For each\n> >           access, the pack file name and an offset in the pack is recorded.\n> >           This may be helpful for troubleshooting some pack-related\n> >           performance problems. See GIT_TRACE for available trace output\n> >           options.\n> >\n> >       GIT_TRACE_PACKET\n> >           Enables trace messages for all packets coming in or out of a given\n> >           program. This can help with debugging object negotiation or other\n> >           protocol issues. Tracing is turned off at a packet starting with\n> >           \"PACK\" (but see GIT_TRACE_PACKFILE below). See GIT_TRACE for\n> >           available trace output options.\n> >\n> >       GIT_TRACE_PACKFILE\n> >           Enables tracing of packfiles sent or received by a given program.\n> >           Unlike other trace output, this trace is verbatim: no headers, and\n> >           no quoting of binary data. You almost certainly want to direct into\n> >           a file (e.g., GIT_TRACE_PACKFILE=/tmp/my.pack) rather than\n> >           displaying it on the terminal or mixing it with other trace output.\n> >\n> >           Note that this is currently only implemented for the client side of\n> >           clones and fetches.\n> >\n> >       GIT_TRACE_PERFORMANCE\n> >           Enables performance related trace messages, e.g. total execution\n> >           time of each Git command. See GIT_TRACE for available trace output\n> >           options.\n> >\n> >       GIT_TRACE_SETUP\n> >           Enables trace messages printing the .git, working tree and current\n> >           working directory after Git has completed its setup phase. See\n> >           GIT_TRACE for available trace output options.\n> >\n> >       GIT_TRACE_SHALLOW\n> >           Enables trace messages that can help debugging fetching / cloning\n> >           of shallow repositories. See GIT_TRACE for available trace output\n> >           options.\n> >\n> >       GIT_TRACE_CURL\n> >           Enables a curl full trace dump of all incoming and outgoing data,\n> >           including descriptive information, of the git transport protocol.\n> >           This is similar to doing curl --trace-ascii on the command line.\n> >           This option overrides setting the GIT_CURL_VERBOSE environment\n> >           variable. See GIT_TRACE for available trace output options.\n> >\n> >       GIT_TRACE_CURL_NO_DATA\n> >           When a curl trace is enabled (see GIT_TRACE_CURL above), do not\n> >           dump data (that is, only dump info lines and headers).\n> >\n> >       GIT_REDACT_COOKIES\n> >           This can be set to a comma-separated list of strings. When a curl\n> >           trace is enabled (see GIT_TRACE_CURL above), whenever a \"Cookies:\"\n> >           header sent by the client is dumped, values of cookies whose key is\n> >           in that list (case-sensitive) are redacted.\n> >\n> >       GIT_LITERAL_PATHSPECS\n> >           Setting this variable to 1 will cause Git to treat all pathspecs\n> >           literally, rather than as glob patterns. For example, running\n> >           GIT_LITERAL_PATHSPECS=1 git log -- '*.c' will search for commits\n> >           that touch the path *.c, not any paths that the glob *.c matches.\n> >           You might want this if you are feeding literal paths to Git (e.g.,\n> >           paths previously given to you by git ls-tree, --raw diff output,\n> >           etc).\n> >\n> >       GIT_GLOB_PATHSPECS\n> >           Setting this variable to 1 will cause Git to treat all pathspecs as\n> >           glob patterns (aka \"glob\" magic).\n> >\n> >       GIT_NOGLOB_PATHSPECS\n> >           Setting this variable to 1 will cause Git to treat all pathspecs as\n> >           literal (aka \"literal\" magic).\n> >\n> >       GIT_ICASE_PATHSPECS\n> >           Setting this variable to 1 will cause Git to treat all pathspecs as\n> >           case-insensitive.\n> >\n> >       GIT_REFLOG_ACTION\n> >           When a ref is updated, reflog entries are created to keep track of\n> >           the reason why the ref was updated (which is typically the name of\n> >           the high-level command that updated the ref), in addition to the\n> >           old and new values of the ref. A scripted Porcelain command can use\n> >           set_reflog_action helper function in git-sh-setup to set its name\n> >           to this variable when it is invoked as the top level command by the\n> >           end user, to be recorded in the body of the reflog.\n> >\n> >       GIT_REF_PARANOIA\n> >           If set to 1, include broken or badly named refs when iterating over\n> >           lists of refs. In a normal, non-corrupted repository, this does\n> >           nothing. However, enabling it may help git to detect and abort some\n> >           operations in the presence of broken refs. Git sets this variable\n> >           automatically when performing destructive operations like git-\n> >           prune(1). You should not need to set it yourself unless you want to\n> >           be paranoid about making sure an operation has touched every ref\n> >           (e.g., because you are cloning a repository to make a backup).\n> >\n> >       GIT_ALLOW_PROTOCOL\n> >           If set to a colon-separated list of protocols, behave as if\n> >           protocol.allow is set to never, and each of the listed protocols\n> >           has protocol.<name>.allow set to always (overriding any existing\n> >           configuration). In other words, any protocol not mentioned will be\n> >           disallowed (i.e., this is a whitelist, not a blacklist). See the\n> >           description of protocol.allow in git-config(1) for more details.\n> >\n> >       GIT_PROTOCOL_FROM_USER\n> >           Set to 0 to prevent protocols used by fetch/push/clone which are\n> >           configured to the user state. This is useful to restrict recursive\n> >           submodule initialization from an untrusted repository or for\n> >           programs which feed potentially-untrusted URLS to git commands. See\n> >           git-config(1) for more details.\n> >\n> >       GIT_PROTOCOL\n> >           For internal use only. Used in handshaking the wire protocol.\n> >           Contains a colon : separated list of keys with optional values\n> >           key[=value]. Presence of unknown keys and values must be ignored.\n> >\n> >       GIT_OPTIONAL_LOCKS\n> >           If set to 0, Git will complete any requested operation without\n> >           performing any optional sub-operations that require taking a lock.\n> >           For example, this will prevent git status from refreshing the index\n> >           as a side effect. This is useful for processes running in the\n> >           background which do not want to cause lock contention with other\n> >           operations on the repository. Defaults to 1.\n> >\n> >       GIT_REDIRECT_STDIN, GIT_REDIRECT_STDOUT, GIT_REDIRECT_STDERR\n> >           Windows-only: allow redirecting the standard input/output/error\n> >           handles to paths specified by the environment variables. This is\n> >           particularly useful in multi-threaded applications where the\n> >           canonical way to pass standard handles via CreateProcess() is not\n> >           an option because it would require the handles to be marked\n> >           inheritable (and consequently every spawned process would inherit\n> >           them, possibly blocking regular Git operations). The primary\n> >           intended use case is to use named pipes for communication (e.g.\n> >           \\\\.\\pipe\\my-git-stdin-123).\n> >\n> >           Two special values are supported: off will simply close the\n> >           corresponding standard handle, and if GIT_REDIRECT_STDERR is 2>&1,\n> >           standard error will be redirected to the same handle as standard\n> >           output.\n> >\n> >       GIT_PRINT_SHA1_ELLIPSIS (deprecated)\n> >           If set to yes, print an ellipsis following an (abbreviated) SHA-1\n> >           value. This affects indications of detached HEADs (git-checkout(1))\n> >           and the raw diff output (git-diff(1)). Printing an ellipsis in the\n> >           cases mentioned is no longer considered adequate and support for it\n> >           is likely to be removed in the foreseeable future (along with the\n> >           variable).\n> >\n> >DISCUSSION\n> >       More detail on the following is available from the Git concepts chapter\n> >       of the user-manual[2] and gitcore-tutorial(7).\n> >\n> >       A Git project normally consists of a working directory with a \".git\"\n> >       subdirectory at the top level. The .git directory contains, among other\n> >       things, a compressed object database representing the complete history\n> >       of the project, an \"index\" file which links that history to the current\n> >       contents of the working tree, and named pointers into that history such\n> >       as tags and branch heads.\n> >\n> >       The object database contains objects of three main types: blobs, which\n> >       hold file data; trees, which point to blobs and other trees to build up\n> >       directory hierarchies; and commits, which each reference a single tree\n> >       and some number of parent commits.\n> >\n> >       The commit, equivalent to what other systems call a \"changeset\" or\n> >       \"version\", represents a step in the project's history, and each parent\n> >       represents an immediately preceding step. Commits with more than one\n> >       parent represent merges of independent lines of development.\n> >\n> >       All objects are named by the SHA-1 hash of their contents, normally\n> >       written as a string of 40 hex digits. Such names are globally unique.\n> >       The entire history leading up to a commit can be vouched for by signing\n> >       just that commit. A fourth object type, the tag, is provided for this\n> >       purpose.\n> >\n> >       When first created, objects are stored in individual files, but for\n> >       efficiency may later be compressed together into \"pack files\".\n> >\n> >       Named pointers called refs mark interesting points in history. A ref\n> >       may contain the SHA-1 name of an object or the name of another ref.\n> >       Refs with names beginning ref/head/ contain the SHA-1 name of the most\n> >       recent commit (or \"head\") of a branch under development. SHA-1 names of\n> >       tags of interest are stored under ref/tags/. A special ref named HEAD\n> >       contains the name of the currently checked-out branch.\n> >\n> >       The index file is initialized with a list of all paths and, for each\n> >       path, a blob object and a set of attributes. The blob object represents\n> >       the contents of the file as of the head of the current branch. The\n> >       attributes (last modified time, size, etc.) are taken from the\n> >       corresponding file in the working tree. Subsequent changes to the\n> >       working tree can be found by comparing these attributes. The index may\n> >       be updated with new content, and new commits may be created from the\n> >       content stored in the index.\n> >\n> >       The index is also capable of storing multiple entries (called \"stages\")\n> >       for a given pathname. These stages are used to hold the various\n> >       unmerged version of a file when a merge is in progress.\n> >\n> >FURTHER DOCUMENTATION\n> >       See the references in the \"description\" section to get started using\n> >       Git. The following is probably more detail than necessary for a\n> >       first-time user.\n> >\n> >       The Git concepts chapter of the user-manual[2] and gitcore-tutorial(7)\n> >       both provide introductions to the underlying Git architecture.\n> >\n> >       See gitworkflows(7) for an overview of recommended workflows.\n> >\n> >       See also the howto[3] documents for some useful examples.\n> >\n> >       The internals are documented in the Git API documentation[4].\n> >\n> >       Users migrating from CVS may also want to read gitcvs-migration(7).\n> >\n> >AUTHORS\n> >       Git was started by Linus Torvalds, and is currently maintained by Junio\n> >       C Hamano. Numerous contributions have come from the Git mailing list\n> >       <git@vger.kernel.org[5]>.\n> >       http://www.openhub.net/p/git/contributors/summary gives you a more\n> >       complete list of contributors.\n> >\n> >       If you have a clone of git.git itself, the output of git-shortlog(1)\n> >       and git-blame(1) can show you the authors for specific parts of the\n> >       project.\n> >\n> >REPORTING BUGS\n> >       Report bugs to the Git mailing list <git@vger.kernel.org[5]> where the\n> >       development and maintenance is primarily done. You do not have to be\n> >       subscribed to the list to send a message there. See the list archive at\n> >       https://public-inbox.org/git for previous bug reports and other\n> >       discussions.\n> >\n> >       Issues which are security relevant should be disclosed privately to the\n> >       Git Security mailing list <git-security@googlegroups.com[6]>.\n> >\n> >SEE ALSO\n> >       gittutorial(7), gittutorial-2(7), giteveryday(7), gitcvs-migration(7),\n> >       gitglossary(7), gitcore-tutorial(7), gitcli(7), The Git User's\n> >       Manual[1], gitworkflows(7)\n> >\n> >GIT\n> >       Part of the git(1) suite\n> >\n> >NOTES\n> >        1. Git User's Manual\n> >           file:///home/frederik/share/doc/git-doc/user-manual.html\n> >\n> >        2. Git concepts chapter of the user-manual\n> >           file:///home/frederik/share/doc/git-doc/user-manual.html#git-concepts\n> >\n> >        3. howto\n> >           file:///home/frederik/share/doc/git-doc/howto-index.html\n> >\n> >        4. Git API documentation\n> >           file:///home/frederik/share/doc/git-doc/technical/api-index.html\n> >\n> >        5. git@vger.kernel.org\n> >           mailto:git@vger.kernel.org\n> >\n> >        6. git-security@googlegroups.com\n> >           mailto:git-security@googlegroups.com\n> >\n> >Git 2.21.0.rc1.9.g3f              02/18/2019                            GIT(1)\n>\n"}]}