I'm working with a large application I've checked out from my repository, the bulk of this app is in the .svn/pristine
folder. From what I understand, the pristine folder contains copies of the files in my workingCopy directory
That being said,
I have my files backed up already and no intention to revert. The extra space gained would dramatically cut my compile time as well.
EDIT
I now understand that changing anything manually inside .svn
will likely break my workingCopy.
I need to find a way to reduce the size of my workingCopy. In TortoiseSVN, there is a Cleanup - Delete unversioned files and folders
, which "removes all generated files in your working copy". Perhaps this would get rid of those files without breaking my application?
Cheers
You must not touch the directory .svn
in your working copy manually. The directory is required for client-side operations.
The .svn
directory stores working copy metadata and pristine copy of WC files for client-side operations only, it must exist in each SVN working copy but not in SVN repository. Storing it in Subversion repository can lead to errors on the client side.
In other words, you must not store the directory .svn
in the repository. If you have this directory in the repository then someone has mistakenly committed it.
See SVNBook | Subversion Working Copies:
A working copy also contains some extra files, created and maintained by Subversion, to help it carry out these commands. In particular, each working copy contains a subdirectory named .svn, also known as the working copy's administrative directory. The files in the administrative directory help Subversion recognize which of your versioned files contain unpublished changes, and which files are out of date with respect to others' work.
svn:ignore
property, files generated after you run build or debug.I guess that you store large binaries in your repository / working copy. I don't think that you'll be able to solve the working copy size issue without reorganizing your SVN repository.