Updating paths is incompatible with switching branchesforcing
Say you have modified two files, ‘README’ and ‘test/basic.t’, then you go to the ‘test’ directory, and run ‘‘, in pre-v2.0 only ‘test/basic.t’ will be staged, in post-v2.0 both files will be staged.
If you run the command in the top level directory, nothing changes.
You can say "git add --ignore-removal " to add only added or modified paths in , if you really want to. Say you removed the file ‘test/basic.t’ and added a new file ‘test/main.t’, those changes are not staged, so you stage them with ‘git add test/’, pre-v2.0 ‘test/basic.t’ would remain tracked, post-v2.0, ‘test/basic.t’ is removed from the stage.
If you haven’t seen the following warning while doing ‘warning: You ran 'git add' with neither '-A (--all)' or '--ignore-removal', whose behaviour will change in Git 2.0 with respect to paths you removed.
Sure, Git v2.0.0 received a good dosage of new features and bug-fixes, but so did v1.9.0, and all the versions before.The default prefix for "git svn" has changed in Git 2.0.