Guten Tag Kenny Raghunath, am Dienstag, 25. September 2012 um 22:21 schrieben Sie:
> Anyone have any suggestions on what I can do to fix this? It's really unlikely Subversion itself is the problem, it surely has something to do with your deployment, working copies, merge strategies or something like that. If I were you I would spent some time reading the logs and especially the diffs per Commit on the reverted code, there surely is some commit which reverts it and from your log message you may get a hint on what exactly you did during the development of this commit. As for your deployment issues, as you say you deploy manually to your production system, you should consider increasing log level of your deployment tool, have a look at timestamps of the reverted code etc. How exactly does your production deployment work and how do you verify? Do you use ssh and verify after restarting you web server by using the production website? Especially on Linux files can be replaced during they are used, but the programs still using them won't see the new verisons unless they open new handles to the files etc. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon.............030-2 1001-310 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
