On Sep 24, 2014, at 9:42 AM, John Maher <jo...@rotair.com> wrote: > Thanks for the link jb. Reading through that section of the book I > encountered "file changes" and "tree changes." It also just mentions > "changes" numerous times. On my initial reading it appears that when the > book mentions "changes" without specifying the type (like the definition of > the "Commit" command) it is talking about "file changes" ONLY and it is > excluding "tree changes." Just wondering if that assumption would be right > most of the time or could it go either way and I would have to test to see > which one was applicable. I tried looking at other mentions of the "changes" > but due to my ignorance of the software I wasn't able to come to any > conclusions myself.
If you issue the 'svn commit' command without specifying any filenames, svn assumes (as a work-flow optimization) that you wish to commit all changes to all tracked files from that point in the file tree, recursively. I say this is an optimization because 'commit' and 'update' are very frequently used in normal subversion activities. By way of contrast, Git assumes nothing, and requires you to explicitly 'git add' any changed files you wish to include in your commit, in addition to any directories or new files you wish to include.
