On Mon, Jan 21, 2013 at 10:23 AM, Junio C Hamano <gits...@pobox.com> wrote: > No. This is only about "git add -u<RETURN>", not any other forms of > "git add ...with or without other args...". > > "git add -u<RETURN>" historically meant, and it still means, to > "update the index with every change in the working tree", even when > you are in a subdirectory.
But it *currently* limits itself to a subdirectory - does not work on whole tree: piotr@PIOTR-X73 ~/dv/test/dir1 (master) $ git status # On branch master # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: dir2/file2.txt # modified: file1.txt # modified: ../file.txt # no changes added to commit (use "git add" and/or "git commit -a") piotr@PIOTR-X73 ~/dv/test/dir1 (master) $ git add -u piotr@PIOTR-X73 ~/dv/test/dir1 (master) $ git status # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # modified: dir2/file2.txt # modified: file1.txt # # Changes not staged for commit: # (use "git add <file>..." to update what will be committed) # (use "git checkout -- <file>..." to discard changes in working directory) # # modified: ../file.txt # piotr@PIOTR-X73 ~/dv/test/dir1 (master) $ git --version git version 1.8.0.msysgit.0 -- Piotr Krukowiecki -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
