Re: git checkout -b following git reset --hard pitfall

"Maris, Rob" writes: > Normally, when there are modifications in the working tree not yet added > resp. committed, git will refuse to change to another branch. Only if switching the branch requires touching the modified files. > Actually, the modified > status of git related to both branches af

git checkout -b following git reset --hard pitfall

Normally, when there are modifications in the working tree not yet added resp. committed, git will refuse to change to another branch. However, when I create a new branch on the fly, using git checkout -b , there is no complaint appearing. After doing so, I executed a git reset --hard in once