Search results for head

  1. Reset Demystified


    ="tableblock">HEAD Last commit snapshot, next parent

  2. Revision Selection


    ="_git_reflog">RefLog Shortnames One of the things Git does in the background while you’re working away is keep a “reflog” — a log of where your HEAD and branch references have

  3. Git References


    ="console">$ echo 1a410efbd13591db07496601ebc7a059dd55cfe9 > .git/refs/heads/master Now, you can use the head reference you just created instead of

  4. Git Aliases


    ="highlight">$ git config --global alias.unstage 'reset HEAD --' This makes the following two

  5. Branches in a Nutshell


    currently on? It keeps a special pointer called HEAD. Note that this is a lot different than the concept of HEAD in other VCSs you may be used to, such as Subversion or CVS. In Git

  6. Rewriting History


    onto the HEAD that they were originally based on instead of moving them to another one. With the interactive rebase tool, you can then stop after each commit you want to modify and change the message

  7. Rerere


    >Another application of rerere is where you merge a bunch of evolving topic branches together into a testable head occasionally, as the Git project itself often does. If the tests fail, you

  8. Libgit2


    ; int error = git_repository_open(&repo, "/path/to/repository"); // Dereference HEAD to a commit git_object *head_commit; error = git_revparse_single(&head_commit, repo, "HEAD^{commit

  9. Plumbing and Porcelain


    " data-lang="console">$ ls -F1 config description HEAD hooks/ info/ objects/ refs/ Depending on your version of Git, you may see some additional

  10. Git as a Client


    ) Checked out HEAD: file:///tmp/test-svn/trunk r75 This runs the equivalent of two commands – git svn init followed by git svn

  11. git-symbolic-ref


    ' [-q] [--short] 'git symbolic-ref' --delete [-q] DESCRIPTION ----------- Given one argument, reads which branch head the given symbolic ref refers to and outputs its path, relative to

  12. trivial-merge


    head or (if the merge is trivial) the result. If multiple cases apply, the one used is listed first. A result of "no merge" means that index is left in stage 0, ancest in stage 1, head in stage 2

  13. git-remote


    ] [--[no-]tags] [--mirror=(fetch|push)] 'git remote rename' 'git remote remove' 'git remote set-head' (-a | --auto | -d | --delete | ) 'git remote set-branches

  14. git-prune


    git-prune(1) ============ NAME ---- git-prune - Prune all unreachable objects from the object database SYNOPSIS -------- [verse] 'git prune' [-n] [-v] [--progress] [--expire ] [--] [

  15. rev-list-description


    [] ----------------------------------------------------------------------- $ git rev-list origin..HEAD $ git rev-list HEAD ^origin ----------------------------------------------------------------------- endif::git-rev-list[] ifdef::git

  16. git-reset


    git-reset(1) ============ NAME ---- git-reset - Reset current HEAD to the specified state SYNOPSIS -------- [verse] 'git reset' [-q] [] [--] ... 'git reset' [-q] [--pathspec

  17. git-cherry


    git-cherry(1) ============= NAME ---- git-cherry - Find commits yet to be applied to upstream SYNOPSIS -------- [verse] 'git cherry' [-v] [ [ []]] DESCRIPTION

  18. git-checkout


    `HEAD` to set the specified branch as the current branch. 'git checkout' []:: To prepare for working on ``, switch to it by updating the index and the files in the working tree, and

  19. git-switch


    `--guess`), or detach the working tree from any branch with `--detach`, along with switching. Switching branches does not require a clean index and working tree (i.e. no differences compared to `HEAD

  20. git-update-ref


    . `git update-ref HEAD ` updates the current branch head to the new object. Given three arguments, stores the in the , possibly dereferencing the symbolic refs, after