<p>A problem I ran into a while back I never found a good solution for...</p>

<p>Say you have a working copy checked out from subversion at revision 7500, and the disk holding the current repository dies. You've got a backup of the repository at, say, revision 7450. It's easy to restore the repository backup, but any attempt to use the working copy against it gives an error saying that revision 7500 doesn't exist in the repository.</p>

<p>What is the best way to check in one gigantic revision to bring the content of the repository up to match the content of the working copy and get he working copy back to a functional state?</p>

<p>(Ideally I'd like something easier than having to check out a brand new working copy and then copying over all the files manually - I think at the time the working copies were used to configuration manage servers, so it was a real pain to have to check out clean working copies)</p>

[{'answer_id': 56544, 'author': 'Ben Scheirman', 'author_id': 3381, 'author_profile': 'https://Stackoverflow.com/users/3381', 'pm_score': 3, 'selected': False, 'text': '<p>Do a fresh checkout into a different folder, then use a diff program to create a patch.  apply the patch to your new working copy.</p>\n'}, {'answer_id': 56552, 'author': 'Grant', 'author_id': 30, 'author_profile': 'https://Stackoverflow.com/users/30', 'pm_score': 4, 'selected': True, 'text': '<p>You could check out a rev.7450 copy somewhere, then export your 7500 copy (to remove the .svn folders). Drag the exported copy (which is the latest copy) over the 7450 copy. All the new files should simply overwrite the older ones, leaving the .svn folders the same. </p>\n\n<p>Subversion will assume you just made a bunch of changes to 7450, and the next checkin will set it as 7451.</p>\n'}, {'answer_id': 56579, 'author': 'Josef', 'author_id': 5581, 'author_profile': 'https://Stackoverflow.com/users/5581', 'pm_score': 1, 'selected': False, 'text': "<p>If you are positive you've got the latest version in your directory, then do this:</p>\n\n<ol>\n<li>Delete the item from the repository</li>\n<li>Delete the SVN references from your copy</li>\n<li>Check your code in as a new copy.</li>\n<li>Check out the code you just checked in</li>\n</ol>\n"}, {'answer_id': 3294944, 'author': 'puetzk', 'author_id': 14312, 'author_profile': 'https://Stackoverflow.com/users/14312', 'pm_score': 1, 'selected': False, 'text': '<p>You can fill in the missing revision numbers by loading in a dump file with a bunch of empty revisions. There are answers discussing how to do this over at <a href="https://stackoverflow.com/questions/435638/how-can-i-change-the-revision-number-of-a-repository-in-tortoise-svn/435692#435692">How can I change the revision number of a repository</a>. Load all but one revision this way, then you can just check in all your changes in one last giant revision.</p>\n'}]
['https://Stackoverflow.com/questions/56543', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/797/']