I believe I figured out why this happens. I was merging from branch to trunk. I noticed some conflicts and realized I hadn’t done something in my branch that I wanted to before I merged. So I “svn revert” all the merge changes (so I did not commit/chick in the merge). Then I made the change I needed in my branch.

I merged from branch to trunk again and this time I got that “skipped” error on a file (file1.cs). When I found your post here I realized what happened.

When I reverted the files instead of merging, it reverted all the files that existed in the trunk already, but it did not revert/remove the new file that came from the branch (file1.cs). So svn was seeing that file there but wasn’t sure what it was. So I had to browse to the file, right-click, and “svn add” the file manually.

So svn “skipped” the file because it was already in the trunk folder, but it wasn’t a conflict/merge because it wasn’t an svn file yet (it had never been checked in to the trunk).

I hope that made sense, and I hope that helps clarify a little more what the “skipped” error means.

So your blog post helped me a great deal, thanks.