> >I believe I have found one mistake in your slides. Slide 18 reads: > >"git-commit -a" is like "git-add .; git-commit" > > > >But it is incorrect, because "git-commit -a" does not add new files, so > >it works like "git-add -u .; git-commit". > > "git-commit -a" also detects files that have been deleted, whereas > "git-add" does not. I just tried "git-add -u ." and it *does* detect deleted files. $ git-status # On branch master nothing to commit (working directory clean) $ rm oldfile $ git-status # On branch master # Changed but not updated: # (use "git add/rm <file>..." to update what will be committed) # # deleted: oldfile # no changes added to commit (use "git add" and/or "git commit -a") $ git-add -u . $ git-status # On branch master # Changes to be committed: # (use "git reset HEAD <file>..." to unstage) # # deleted: oldfile # $ git-commit Created commit 17e2bba: delete 1 files changed, 0 insertions(+), 1 deletions(-) delete mode 100644 oldfile So, it works exactly as "git-commit -a" in this case. Dmitry - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html