I was trapped by the following scenario:
I had a new set update to the production version, let's say revision 371
A couple of changes is just reverting files back to revision 369. So I just revert the "files in my working" copy back to revision 369.
Few weeks later client approved all changes and the request me to implement.
I Just right click My working copy and run "Check for modifications", the changes files listed would is transferred to Pro Duction environment.
However today I realised the file revertted back to revision 369 were not implemented. I thought it is just my oversight and isn't see those changes.
But the reverted file does have a green tick meaning there were no changes to them.
After reading the explaination on the web, It shows the revert file is not treated as changes.
*** I learnt that we also need to run ' check for modifications ' then click 'check Repository' and this can show the D Ifference to the latest version on repository.
To prevent the issue and does the committable revert, following inform works for me:
Http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-howto-rollback.html
Roll Back (Undo) revisions in the repository
Use the Revision Log dialog
By far the easiest-revert the changes from one or more revisions, are to use the Revision Log dialog.
Select the file or folder in which your need to revert the changes. If you want to revert all changes, this should is the top level folder.
Select tortoisesvn→ Show Log to display a list of revisions. Need to use Show all or Next to show the revision (s) is interested in.
Select the revision wish to revert. If you want to undo a range of revisions, select the first one and holding the Shift key while selecting the Las T one. If you want to pick out individual revisions and ranges, use the Ctrl key while selecting revisions. Right click on the selected revision (s) and then select Context menu→ Revert changes from this revision.
Or If you want a earlier revision the new HEAD revision, right click on the selected revision and then select context menu→ Revert to this revision. This would discard all changes after the selected revision.
You have reverted the changes within your working copy. Check the results, then commit the changes.
Use the Merge dialog
If you want to enter revision numbers as a list, you can use the Merge dialog. The previous method uses merging behind the scenes; This method uses it explicitly.
In your working copy select tortoisesvn→ Merge.
In the Merge Type dialog Select Merge a range of revisions.
In the From:field enter the full repository URL of your working copy folder. This should come up as the default URL.
In the Revision range to merge field enter the list of revisions to roll back (or use the log dialog to select them as described above).
Make sure the Reverse merge checkbox is checked.
In the Merge Options dialog accept the defaults.
Click Merge to complete the merge.
You have reverted the changes within your working copy. Check that the results is as expected, then commit the changes.
Use
svndumpfilter
Since TortoiseSVN never loses data, your "rolled back" revisions still exist as intermediate revisions in the repo Sitory. Only the HEAD revision is changed to a previous state. If you want to make revisions disappear completely from your repository, erasing all trace that they ever existed, you hav E to use more extreme measures. Unless there is a really good reason to does this, it's not recommended. One possible reason would be, someone committed a confidential document to a public repository.
The only-to-remove data from the repository are to use the Subversion command line tool svnadmin
. You can find a description of about this works in the Repository maintenance .
Subversion Revert File is not being shown in modification