Changes between Version 11 and Version 12 of versionControl/git


Ignore:
Timestamp:
Jul 25, 2016 6:28:09 PM (5 years ago)
Author:
minondoa
Comment:

One of the explanations was duplicated and another one seemed to be in a different order than the one intended.

Legend:

Unmodified
Added
Removed
Modified
  • versionControl/git

    v11 v12  
    411411
    412412{{{
     413git checkout <commit> <file>
     414}}}
     415
     416Create and check out <new-branch>.
     417
     418{{{
    413419git checkout -b <new-branch>
    414420}}}
    415421
    416 Create and check out <new-branch>.
    417 
    418 {{{
    419 git checkout <commit> <file>
    420 }}}
    421 
    422 Check out a previous version of a file. This turns the <file> that resides in the working directory into an exact copy of the one from <commit> and adds it to the staging area.
     422Update all files in the working directory to match the specified commit.
    423423
    424424{{{
     
    426426}}}
    427427
    428 Update all files in the working directory to match the specified commit. You can use either a commit hash or a tag as the <commit> argument. This will put you in a detached HEAD state. During the normal course of development, the HEAD usually points to master or some other local branch, but when you check out a previous commit, HEAD no longer points to a branch—it points directly to a commit. This is called a “detached HEAD” state.
     428You can use either a commit hash or a tag as the <commit> argument. This will put you in a detached HEAD state. During the normal course of development, the HEAD usually points to master or some other local branch, but when you check out a previous commit, HEAD no longer points to a branch—it points directly to a commit. This is called a “detached HEAD” state.
    429429
    430430