Hey guys,
Ran into a problem, and hoping someone can give me the long shot I need to resolve it. One of our junior engineers was kind enough to check in hundreds of breaking file changes. I can revert the project to the last stable revision without problem and the project runs perfectly on my local client. Problem seems to be that it doesn’t register any of the reverted files in my local changes, which means I can’t commit the stable version. The immediate solution that came to mind was to touch the reverted files so that they become flagged as changed. However, I’d rather not iterate through hundreds of files to do this if I can avoid it. So, question I guess boils down to: How do I flag reverted files as changed so that I can commit them, without manually touching every file?
License info:
Unity (Pro) 4.1.2f1
Asset Server + Team License
Thank you for your help,
Memige Den Adel
LOOT Entertainment | SonyDADC New Media Solutions
EDIT: misunderstood initial issue:
- copy over the (working) project to a different file location.
- update to the current build
- either copy the files back, or do a directory comparison with something like WinMerge to replace the files that “need” to be reverted
this way you don’t have to manually insert/delete a blank line in each file. had to do this twice when a massive new feature had to be removed, and then put back in (still don’t like that PM)
this is to revert local project to revisionX
in “show history” find the revision you want to revert to. in the bottom right corner there is a button “revert Entire Project to ####” not sure if this is an irreversible modification.
the last time we had an issue where the server was causing problems (conflict of creation and destruction of files) we had to essentially restart the project (take the last fully functional build, and start a new asset server instance)
as a side note have this junior dev fix the errors that s/he made, or maybe they placed a needed file as a commit exception.