Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i think these should be two different HEADS, so why they corresponds to the same sha value, that is 2aad8cb …
git reflog
2aad8cb HEAD@{0}: checkout: moving from master to xxx_master
2aad8cb HEAD@{1}: clone: from git@github.com:xxx/xxx.git
When you first create a new branch via
git branch newbranchorgit checkout -b newbranch master,newbranchwill point to exactly the same commit as the branch point (whatever HEAD was in the first example, ormasterin the second). So it would be normal to see, for example,masterandnewbranchboth having the same SHA. When you create a new commit on either branch, then that branch will point to the new commit, which will have the previous value as its parent (over-simplifying to avoid discussing merges, etc.).