Re: Perplexing results of SVN commit
From: Ryan Schmidt <subversion-2011a_at_ryandesign.com>
Date: Mon, 11 Jul 2011 21:13:22 -0500
On Jul 11, 2011, at 14:07, Warren Jones wrote:
> One of our developers got perplexing results from an SVN commit. As far as I can tell, this is what happened:
Sounds to me like operator error of the following kind: the developer modified the files in the working copy, and also made identical modifications to the corresponding pristine files in .svn/text-base (frequently this happens when using a batch search-replace tool). Because even after the edits the contents of the pristine files match the regular files, "svn st" and "svn di" don't show the changes and they don't get committed.
If this is what happened, check out a fresh working copy, manually copy over the changed files, and commit them. And ensure that in the future you do not edit anything in the .svn directories. Some batch search-replace tools let you define directories they're not to touch.
This is an archived mail posted to the Subversion Users mailing list.