It not clear what was the first step which 'broke' the working copy you have, however I guess that you should use vendor branching strategy to avoid such issues in future. (I may be wrong here because I don't understand those steps that you describe as "resulting in a less than happy svn-database").
As of svn:ignore
property, it affects unversioned items in your working copy only:
Subversion's support for ignorable file patterns extends only to the one-time process of adding unversioned files and directories to version control. Once an object is under Subversion's control, the ignore pattern mechanisms no longer apply to it. In other words, don't expect Subversion to avoid committing changes you've made to a versioned file simply because that file's name matches an ignore pattern—Subversion always notices all of its versioned objects.
You have to set svn:ignore
or svn:global-ignores
(requires SVN 1.8+ client) before you add your project's items to Subversion repository. I.e. the workflow should be as follows:
svn checkout
a working copy of a repository path where you plan to put your project's items,- In the working copy, run
svn propset svn:ignore --recursive --file _svn-ign . > svn-ignore-ausgabe.txt 2>&
, - Use
svn add
to your project's items to version-control. You'll notice that items that match the ignore pattern fromsvn:ignore
are not added. svn commit
new revision to the repository.
Read SVNBook!
Thank you for the answer.
Amazing answer !