![]() ![]() ![]() Changes to a branch may eventually be merged back into another branch to unify them. A branch represents a separate thread of development that may run concurrently with other development efforts on the same code base. It can also contain a (PGP) signature, in which case it is called a "signed tag object".Ī tag represents a version of a particular branch at a moment in time. A tag is most typically used to mark a particular point in the commit ancestry chain.Īn object containing a ref pointing to another object, which can contain a message just like a commit object. Tags (not tag objects) are stored in $GIT_DIR/refs/tags/. In contrast to a head, a tag is not changed by a commit. A single git repository can track an arbitrary number of branches, but your working tree is associated with just one of them (the "current" or "checked out" branch), and HEAD points to that branch.Ī ref pointing to a tag or commit object. The tip of the branch is referenced by a branch head, which moves forward as additional development is done on the branch. The most recent commit on a branch is referred to as the tip of that branch. Ī "branch" is an active line of development. remote-tracking branches reside in refs/remotes// namespace, and follow ordinary branches in remote repository.The HEAD pointer must refer to a branch (symbolic reference) or directly to a commit (detached HEAD or unnamed branch). branches reside in refs/heads/ namespace, and can point only to commit objects.tags reside in refs/tags/ namespace, and can point to tag objects (annotated and optionally GPG signed tags) or directly to commit object (less used lightweight tag for local names), or in very rare cases even to tree object or blob object (e.g. ![]() The branch pointer naturally advances, pointing to newer and newer commits. New commits are created on top of branch. branches are symbolic names for line of development.They always point to the same object (usually: to the same revision) they do not change. tags are symbolic names for a given revision.The "detached at" or "detached from" state is computed by scanning the reflog for HEAD, so it's not 100% reliable depending on just what you get stuck into the reflog. 2.6.2: git status no longer says the useless HEAD detached at HEAD.2.5.0: git status says more about an ongoing interactive rebase.2.4.0: git status learned -v -v, and its detached at / detached from is improved and synchronized with that of git branch.1.8.5: git status improved several reports: submodules, cherry-picks, and status of the current branch (if any) with respect to its upstream.1.8.4: git status learned configuration options status.branch and status.short.1.8.3: git status learned to report about being in the middle of a git revert, too.1.8.2: git status learned to say which branch is being bisected or rebased, during these operations.1.7.11.3: git status (and git diff itself) fixed to handle files named. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |