{
    "content": [
        {
            "type": "text",
            "text": "# GITGLOSSARY (info)\n\n## NAME\n\ngitglossary - A Git Glossary\n\n## SYNOPSIS\n\n*\n\n## DESCRIPTION\n\nalternate object database\nVia the alternates mechanism, a repository can inherit part of its\nobject database from another object database, which is called an\n\"alternate\".\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **SEE ALSO**\n- **GIT**\n- **NOTES**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "GITGLOSSARY",
        "section": "",
        "mode": "info",
        "summary": "gitglossary - A Git Glossary",
        "synopsis": "*",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "gittutorial",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/gittutorial/7/json"
            },
            {
                "name": "gittutorial-2",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/gittutorial-2/7/json"
            },
            {
                "name": "gitcvs-migration",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/gitcvs-migration/7/json"
            },
            {
                "name": "giteveryday",
                "section": "7",
                "url": "https://www.chedong.com/phpMan.php/man/giteveryday/7/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 599,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "GIT",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "NOTES",
                "lines": 4,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "gitglossary - A Git Glossary\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "*\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "alternate object database\nVia the alternates mechanism, a repository can inherit part of its\nobject database from another object database, which is called an\n\"alternate\".\n\nbare repository\nA bare repository is normally an appropriately named directory with\na .git suffix that does not have a locally checked-out copy of any\nof the files under revision control. That is, all of the Git\nadministrative and control files that would normally be present in\nthe hidden .git sub-directory are directly present in the\nrepository.git directory instead, and no other files are present\nand checked out. Usually publishers of public repositories make\nbare repositories available.\n\nblob object\nUntyped object, e.g. the contents of a file.\n\nbranch\nA \"branch\" is a line of development. The most recent commit on a\nbranch is referred to as the tip of that branch. The tip of the\nbranch is referenced by a branch head, which moves forward as\nadditional development is done on the branch. A single Git\nrepository can track an arbitrary number of branches, but your\nworking tree is associated with just one of them (the \"current\" or\n\"checked out\" branch), and HEAD points to that branch.\n\ncache\nObsolete for: index.\n\nchain\nA list of objects, where each object in the list contains a\nreference to its successor (for example, the successor of a commit\ncould be one of its parents).\n\nchangeset\nBitKeeper/cvsps speak for \"commit\". Since Git does not store\nchanges, but states, it really does not make sense to use the term\n\"changesets\" with Git.\n\ncheckout\nThe action of updating all or part of the working tree with a tree\nobject or blob from the object database, and updating the index and\nHEAD if the whole working tree has been pointed at a new branch.\n\ncherry-picking\nIn SCM jargon, \"cherry pick\" means to choose a subset of changes\nout of a series of changes (typically commits) and record them as a\nnew series of changes on top of a different codebase. In Git, this\nis performed by the \"git cherry-pick\" command to extract the change\nintroduced by an existing commit and to record it based on the tip\nof the current branch as a new commit.\n\nclean\nA working tree is clean, if it corresponds to the revision\nreferenced by the current head. Also see \"dirty\".\n\ncommit\nAs a noun: A single point in the Git history; the entire history of\na project is represented as a set of interrelated commits. The word\n\"commit\" is often used by Git in the same places other revision\ncontrol systems use the words \"revision\" or \"version\". Also used as\na short hand for commit object.\n\nAs a verb: The action of storing a new snapshot of the project's\nstate in the Git history, by creating a new commit representing the\ncurrent state of the index and advancing HEAD to point at the new\ncommit.\n\ncommit object\nAn object which contains the information about a particular\nrevision, such as parents, committer, author, date and the tree\nobject which corresponds to the top directory of the stored\nrevision.\n\ncommit-ish (also committish)\nA commit object or an object that can be recursively dereferenced\nto a commit object. The following are all commit-ishes: a commit\nobject, a tag object that points to a commit object, a tag object\nthat points to a tag object that points to a commit object, etc.\n\ncore Git\nFundamental data structures and utilities of Git. Exposes only\nlimited source code management tools.\n\nDAG\nDirected acyclic graph. The commit objects form a directed acyclic\ngraph, because they have parents (directed), and the graph of\ncommit objects is acyclic (there is no chain which begins and ends\nwith the same object).\n\ndangling object\nAn unreachable object which is not reachable even from other\nunreachable objects; a dangling object has no references to it from\nany reference or object in the repository.\n\ndetached HEAD\nNormally the HEAD stores the name of a branch, and commands that\noperate on the history HEAD represents operate on the history\nleading to the tip of the branch the HEAD points at. However, Git\nalso allows you to check out an arbitrary commit that isn't\nnecessarily the tip of any particular branch. The HEAD in such a\nstate is called \"detached\".\n\nNote that commands that operate on the history of the current\nbranch (e.g.  git commit to build a new history on top of it) still\nwork while the HEAD is detached. They update the HEAD to point at\nthe tip of the updated history without affecting any branch.\nCommands that update or inquire information about the current\nbranch (e.g.  git branch --set-upstream-to that sets what\nremote-tracking branch the current branch integrates with)\nobviously do not work, as there is no (real) current branch to ask\nabout in this state.\n\ndirectory\nThe list you get with \"ls\" :-)\n\ndirty\nA working tree is said to be \"dirty\" if it contains modifications\nwhich have not been committed to the current branch.\n\nevil merge\nAn evil merge is a merge that introduces changes that do not appear\nin any parent.\n\nfast-forward\nA fast-forward is a special type of merge where you have a revision\nand you are \"merging\" another branch's changes that happen to be a\ndescendant of what you have. In such a case, you do not make a new\nmerge commit but instead just update your branch to point at the\nsame revision as the branch you are merging. This will happen\nfrequently on a remote-tracking branch of a remote repository.\n\nfetch\nFetching a branch means to get the branch's head ref from a remote\nrepository, to find out which objects are missing from the local\nobject database, and to get them, too. See also git-fetch(1).\n\nfile system\nLinus Torvalds originally designed Git to be a user space file\nsystem, i.e. the infrastructure to hold files and directories. That\nensured the efficiency and speed of Git.\n\nGit archive\nSynonym for repository (for arch people).\n\ngitfile\nA plain file .git at the root of a working tree that points at the\ndirectory that is the real repository.\n\ngrafts\nGrafts enables two otherwise different lines of development to be\njoined together by recording fake ancestry information for commits.\nThis way you can make Git pretend the set of parents a commit has\nis different from what was recorded when the commit was created.\nConfigured via the .git/info/grafts file.\n\nNote that the grafts mechanism is outdated and can lead to problems\ntransferring objects between repositories; see git-replace(1) for a\nmore flexible and robust system to do the same thing.\n\nhash\nIn Git's context, synonym for object name.\n\nhead\nA named reference to the commit at the tip of a branch. Heads are\nstored in a file in $GITDIR/refs/heads/ directory, except when\nusing packed refs. (See git-pack-refs(1).)\n\nHEAD\nThe current branch. In more detail: Your working tree is normally\nderived from the state of the tree referred to by HEAD. HEAD is a\nreference to one of the heads in your repository, except when using\na detached HEAD, in which case it directly references an arbitrary\ncommit.\n\nhead ref\nA synonym for head.\n\nhook\nDuring the normal execution of several Git commands, call-outs are\nmade to optional scripts that allow a developer to add\nfunctionality or checking. Typically, the hooks allow for a command\nto be pre-verified and potentially aborted, and allow for a\npost-notification after the operation is done. The hook scripts are\nfound in the $GITDIR/hooks/ directory, and are enabled by simply\nremoving the .sample suffix from the filename. In earlier versions\nof Git you had to make them executable.\n\nindex\nA collection of files with stat information, whose contents are\nstored as objects. The index is a stored version of your working\ntree. Truth be told, it can also contain a second, and even a third\nversion of a working tree, which are used when merging.\n\nindex entry\nThe information regarding a particular file, stored in the index.\nAn index entry can be unmerged, if a merge was started, but not yet\nfinished (i.e. if the index contains multiple versions of that\nfile).\n\nmaster\nThe default development branch. Whenever you create a Git\nrepository, a branch named \"master\" is created, and becomes the\nactive branch. In most cases, this contains the local development,\nthough that is purely by convention and is not required.\n\nmerge\nAs a verb: To bring the contents of another branch (possibly from\nan external repository) into the current branch. In the case where\nthe merged-in branch is from a different repository, this is done\nby first fetching the remote branch and then merging the result\ninto the current branch. This combination of fetch and merge\noperations is called a pull. Merging is performed by an automatic\nprocess that identifies changes made since the branches diverged,\nand then applies all those changes together. In cases where changes\nconflict, manual intervention may be required to complete the\nmerge.\n\nAs a noun: unless it is a fast-forward, a successful merge results\nin the creation of a new commit representing the result of the\nmerge, and having as parents the tips of the merged branches. This\ncommit is referred to as a \"merge commit\", or sometimes just a\n\"merge\".\n\nobject\nThe unit of storage in Git. It is uniquely identified by the SHA-1\nof its contents. Consequently, an object cannot be changed.\n\nobject database\nStores a set of \"objects\", and an individual object is identified\nby its object name. The objects usually live in $GITDIR/objects/.\n\nobject identifier\nSynonym for object name.\n\nobject name\nThe unique identifier of an object. The object name is usually\nrepresented by a 40 character hexadecimal string. Also colloquially\ncalled SHA-1.\n\nobject type\nOne of the identifiers \"commit\", \"tree\", \"tag\" or \"blob\" describing\nthe type of an object.\n\noctopus\nTo merge more than two branches.\n\norigin\nThe default upstream repository. Most projects have at least one\nupstream project which they track. By default origin is used for\nthat purpose. New upstream updates will be fetched into\nremote-tracking branches named origin/name-of-upstream-branch,\nwhich you can see using git branch -r.\n\noverlay\nOnly update and add files to the working directory, but don't\ndelete them, similar to how cp -R would update the contents in the\ndestination directory. This is the default mode in a checkout when\nchecking out files from the index or a tree-ish. In contrast,\nno-overlay mode also deletes tracked files not present in the\nsource, similar to rsync --delete.\n\npack\nA set of objects which have been compressed into one file (to save\nspace or to transmit them efficiently).\n\npack index\nThe list of identifiers, and other information, of the objects in a\npack, to assist in efficiently accessing the contents of a pack.\n\npathspec\nPattern used to limit paths in Git commands.\n\nPathspecs are used on the command line of \"git ls-files\", \"git\nls-tree\", \"git add\", \"git grep\", \"git diff\", \"git checkout\", and\nmany other commands to limit the scope of operations to some subset\nof the tree or worktree. See the documentation of each command for\nwhether paths are relative to the current directory or toplevel.\nThe pathspec syntax is as follows:\n\no   any path matches itself\n\no   the pathspec up to the last slash represents a directory\nprefix. The scope of that pathspec is limited to that subtree.\n\no   the rest of the pathspec is a pattern for the remainder of the\npathname. Paths relative to the directory prefix will be\nmatched against that pattern using fnmatch(3); in particular, *\nand ?  can match directory separators.\n\nFor example, Documentation/*.jpg will match all .jpg files in the\nDocumentation subtree, including\nDocumentation/chapter1/figure1.jpg.\n\nA pathspec that begins with a colon : has special meaning. In the\nshort form, the leading colon : is followed by zero or more \"magic\nsignature\" letters (which optionally is terminated by another colon\n:), and the remainder is the pattern to match against the path. The\n\"magic signature\" consists of ASCII symbols that are neither\nalphanumeric, glob, regex special characters nor colon. The\noptional colon that terminates the \"magic signature\" can be omitted\nif the pattern begins with a character that does not belong to\n\"magic signature\" symbol set and is not a colon.\n\nIn the long form, the leading colon : is followed by an open\nparenthesis (, a comma-separated list of zero or more \"magic\nwords\", and a close parentheses ), and the remainder is the pattern\nto match against the path.\n\nA pathspec with only a colon means \"there is no pathspec\". This\nform should not be combined with other pathspec.\n\ntop\nThe magic word top (magic signature: /) makes the pattern match\nfrom the root of the working tree, even when you are running\nthe command from inside a subdirectory.\n\nliteral\nWildcards in the pattern such as * or ?  are treated as literal\ncharacters.\n\nicase\nCase insensitive match.\n\nglob\nGit treats the pattern as a shell glob suitable for consumption\nby fnmatch(3) with the FNMPATHNAME flag: wildcards in the\npattern will not match a / in the pathname. For example,\n\"Documentation/*.html\" matches \"Documentation/git.html\" but not\n\"Documentation/ppc/ppc.html\" or\n\"tools/perf/Documentation/perf.html\".\n\nTwo consecutive asterisks (\"\") in patterns matched against\nfull pathname may have special meaning:\n\no   A leading \"\" followed by a slash means match in all\ndirectories. For example, \"/foo\" matches file or\ndirectory \"foo\" anywhere, the same as pattern \"foo\".\n\"/foo/bar\" matches file or directory \"bar\" anywhere that\nis directly under directory \"foo\".\n\no   A trailing \"/\" matches everything inside. For example,\n\"abc/\" matches all files inside directory \"abc\", relative\nto the location of the .gitignore file, with infinite\ndepth.\n\no   A slash followed by two consecutive asterisks then a slash\nmatches zero or more directories. For example, \"a//b\"\nmatches \"a/b\", \"a/x/b\", \"a/x/y/b\" and so on.\n\no   Other consecutive asterisks are considered invalid.\n\nGlob magic is incompatible with literal magic.\n\nattr\nAfter attr: comes a space separated list of \"attribute\nrequirements\", all of which must be met in order for the path\nto be considered a match; this is in addition to the usual\nnon-magic pathspec pattern matching. See gitattributes(5).\n\nEach of the attribute requirements for the path takes one of\nthese forms:\n\no   \"ATTR\" requires that the attribute ATTR be set.\n\no   \"-ATTR\" requires that the attribute ATTR be unset.\n\no   \"ATTR=VALUE\" requires that the attribute ATTR be set to the\nstring VALUE.\n\no   \"!ATTR\" requires that the attribute ATTR be unspecified.\n\nNote that when matching against a tree object, attributes\nare still obtained from working tree, not from the given\ntree object.\n\nexclude\nAfter a path matches any non-exclude pathspec, it will be run\nthrough all exclude pathspecs (magic signature: !  or its\nsynonym ^). If it matches, the path is ignored. When there is\nno non-exclude pathspec, the exclusion is applied to the result\nset as if invoked without any pathspec.\n\nparent\nA commit object contains a (possibly empty) list of the logical\npredecessor(s) in the line of development, i.e. its parents.\n\npickaxe\nThe term pickaxe refers to an option to the diffcore routines that\nhelp select changes that add or delete a given text string. With\nthe --pickaxe-all option, it can be used to view the full changeset\nthat introduced or removed, say, a particular line of text. See\ngit-diff(1).\n\nplumbing\nCute name for core Git.\n\nporcelain\nCute name for programs and program suites depending on core Git,\npresenting a high level access to core Git. Porcelains expose more\nof a SCM interface than the plumbing.\n\nper-worktree ref\nRefs that are per-worktree, rather than global. This is presently\nonly HEAD and any refs that start with refs/bisect/, but might\nlater include other unusual refs.\n\npseudoref\nPseudorefs are a class of files under $GITDIR which behave like\nrefs for the purposes of rev-parse, but which are treated specially\nby git. Pseudorefs both have names that are all-caps, and always\nstart with a line consisting of a SHA-1 followed by whitespace. So,\nHEAD is not a pseudoref, because it is sometimes a symbolic ref.\nThey might optionally contain some additional data.  MERGEHEAD and\nCHERRYPICKHEAD are examples. Unlike per-worktree refs, these\nfiles cannot be symbolic refs, and never have reflogs. They also\ncannot be updated through the normal ref update machinery. Instead,\nthey are updated by directly writing to the files. However, they\ncan be read as if they were refs, so git rev-parse MERGEHEAD will\nwork.\n\npull\nPulling a branch means to fetch it and merge it. See also git-\npull(1).\n\npush\nPushing a branch means to get the branch's head ref from a remote\nrepository, find out if it is an ancestor to the branch's local\nhead ref, and in that case, putting all objects, which are\nreachable from the local head ref, and which are missing from the\nremote repository, into the remote object database, and updating\nthe remote head ref. If the remote head is not an ancestor to the\nlocal head, the push fails.\n\nreachable\nAll of the ancestors of a given commit are said to be \"reachable\"\nfrom that commit. More generally, one object is reachable from\nanother if we can reach the one from the other by a chain that\nfollows tags to whatever they tag, commits to their parents or\ntrees, and trees to the trees or blobs that they contain.\n\nrebase\nTo reapply a series of changes from a branch to a different base,\nand reset the head of that branch to the result.\n\nref\nA name that begins with refs/ (e.g.  refs/heads/master) that points\nto an object name or another ref (the latter is called a symbolic\nref). For convenience, a ref can sometimes be abbreviated when used\nas an argument to a Git command; see gitrevisions(7) for details.\nRefs are stored in the repository.\n\nThe ref namespace is hierarchical. Different subhierarchies are\nused for different purposes (e.g. the refs/heads/ hierarchy is used\nto represent local branches).\n\nThere are a few special-purpose refs that do not begin with refs/.\nThe most notable example is HEAD.\n\nreflog\nA reflog shows the local \"history\" of a ref. In other words, it can\ntell you what the 3rd last revision in this repository was, and\nwhat was the current state in this repository, yesterday 9:14pm.\nSee git-reflog(1) for details.\n\nrefspec\nA \"refspec\" is used by fetch and push to describe the mapping\nbetween remote ref and local ref.\n\nremote repository\nA repository which is used to track the same project but resides\nsomewhere else. To communicate with remotes, see fetch or push.\n\nremote-tracking branch\nA ref that is used to follow changes from another repository. It\ntypically looks like refs/remotes/foo/bar (indicating that it\ntracks a branch named bar in a remote named foo), and matches the\nright-hand-side of a configured fetch refspec. A remote-tracking\nbranch should not contain direct modifications or have local\ncommits made to it.\n\nrepository\nA collection of refs together with an object database containing\nall objects which are reachable from the refs, possibly accompanied\nby meta data from one or more porcelains. A repository can share an\nobject database with other repositories via alternates mechanism.\n\nresolve\nThe action of fixing up manually what a failed automatic merge left\nbehind.\n\nrevision\nSynonym for commit (the noun).\n\nrewind\nTo throw away part of the development, i.e. to assign the head to\nan earlier revision.\n\nSCM\nSource code management (tool).\n\nSHA-1\n\"Secure Hash Algorithm 1\"; a cryptographic hash function. In the\ncontext of Git used as a synonym for object name.\n\nshallow clone\nMostly a synonym to shallow repository but the phrase makes it more\nexplicit that it was created by running git clone --depth=...\ncommand.\n\nshallow repository\nA shallow repository has an incomplete history some of whose\ncommits have parents cauterized away (in other words, Git is told\nto pretend that these commits do not have the parents, even though\nthey are recorded in the commit object). This is sometimes useful\nwhen you are interested only in the recent history of a project\neven though the real history recorded in the upstream is much\nlarger. A shallow repository is created by giving the --depth\noption to git-clone(1), and its history can be later deepened with\ngit-fetch(1).\n\nstash entry\nAn object used to temporarily store the contents of a dirty working\ndirectory and the index for future reuse.\n\nsubmodule\nA repository that holds the history of a separate project inside\nanother repository (the latter of which is called superproject).\n\nsuperproject\nA repository that references repositories of other projects in its\nworking tree as submodules. The superproject knows about the names\nof (but does not hold copies of) commit objects of the contained\nsubmodules.\n\nsymref\nSymbolic reference: instead of containing the SHA-1 id itself, it\nis of the format ref: refs/some/thing and when referenced, it\nrecursively dereferences to this reference.  HEAD is a prime\nexample of a symref. Symbolic references are manipulated with the\ngit-symbolic-ref(1) command.\n\ntag\nA ref under refs/tags/ namespace that points to an object of an\narbitrary type (typically a tag points to either a tag or a commit\nobject). In contrast to a head, a tag is not updated by the commit\ncommand. A Git tag has nothing to do with a Lisp tag (which would\nbe called an object type in Git's context). A tag is most typically\nused to mark a particular point in the commit ancestry chain.\n\ntag object\nAn object containing a ref pointing to another object, which can\ncontain a message just like a commit object. It can also contain a\n(PGP) signature, in which case it is called a \"signed tag object\".\n\ntopic branch\nA regular Git branch that is used by a developer to identify a\nconceptual line of development. Since branches are very easy and\ninexpensive, it is often desirable to have several small branches\nthat each contain very well defined concepts or small incremental\nyet related changes.\n\ntree\nEither a working tree, or a tree object together with the dependent\nblob and tree objects (i.e. a stored representation of a working\ntree).\n\ntree object\nAn object containing a list of file names and modes along with refs\nto the associated blob and/or tree objects. A tree is equivalent to\na directory.\n\ntree-ish (also treeish)\nA tree object or an object that can be recursively dereferenced to\na tree object. Dereferencing a commit object yields the tree object\ncorresponding to the revision's top directory. The following are\nall tree-ishes: a commit-ish, a tree object, a tag object that\npoints to a tree object, a tag object that points to a tag object\nthat points to a tree object, etc.\n\nunmerged index\nAn index which contains unmerged index entries.\n\nunreachable object\nAn object which is not reachable from a branch, tag, or any other\nreference.\n\nupstream branch\nThe default branch that is merged into the branch in question (or\nthe branch in question is rebased onto). It is configured via\nbranch.<name>.remote and branch.<name>.merge. If the upstream\nbranch of A is origin/B sometimes we say \"A is tracking origin/B\".\n\nworking tree\nThe tree of actual checked out files. The working tree normally\ncontains the contents of the HEAD commit's tree, plus any local\nchanges that you have made but not yet committed.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "gittutorial(7), gittutorial-2(7), gitcvs-migration(7), giteveryday(7),\nThe Git User's Manual[1]\n",
                "subsections": []
            },
            "GIT": {
                "content": "Part of the git(1) suite\n",
                "subsections": []
            },
            "NOTES": {
                "content": "1. The Git User's Manual\nfile:///usr/share/doc/git/html/user-manual.html\n\nGit 2.34.1                        02/26/2026                    GITGLOSSARY(7)",
                "subsections": []
            }
        }
    }
}