Subversion rollback

Somebody recently rolled back Subversion to 04/22.  Could we have an explanation please?

how would someone do that, wouldn’t that be show in the changes list (except a server backup would have been restored of course)?

Were there any commits between 22 and today at all?

Core-Dump said:

how would someone do that, wouldn't that be show in the changes list (except a server backup would have been restored of course)?
Were there any commits between 22 and today at all?


I'm talking about a repository rollback.  Yes, there was one.  Yes, I had at least one commit, which others had pulled from Subversion, used, and discussed.  I will piece together my changes from the diff I posted in a forum and repeat my work.

It's possible, though unlikely, that they had some catastrophe at Google and somebody unrelated to jME rolled us back.  In itself this isn't very unlikely, but it's very unlikely that Google would do it without notifying project admins.

i'm receiving a daily notification email from check-ins, and the last i received is from 23.4.


http://groups.google.com/group/jmonkeyengine-notification?hl=en

Today's most active topics:

* r4289 - Fix NPE bug that arises when trying to save a SpatialTransformer. - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/bb335a0c7815d4ca?hl=en
* r4290 - Removed obsolete variable - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/5c09aa91f3c3e700?hl=en
* r4291 - The node for the armature itself is now being saved correctly AFAIK. - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/54fbf8761525c727?hl=en



If there would have been other commits there should be en email.
So either no commits have been done or google had a problem.
Core-Dump said:

i'm receiving a daily notification email from check-ins, and the last i received is from 23.4.

http://groups.google.com/group/jmonkeyengine-notification?hl=en

Today's most active topics:

* r4289 - Fix NPE bug that arises when trying to save a SpatialTransformer. - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/bb335a0c7815d4ca?hl=en
* r4290 - Removed obsolete variable - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/5c09aa91f3c3e700?hl=en
* r4291 - The node for the armature itself is now being saved correctly AFAIK. - 1 new
  http://groups.google.com/group/jmonkeyengine-notification/t/54fbf8761525c727?hl=en



If there would have been other commits there should be en email.
So either no commits have been done or google had a problem.


I made another commit shortly after those.  The discussion at http://www.jmonkeyengine.com/jmeforum/index.php?topic=10989.0 is about my committed work, and you can see in the final bullet of my last reply there, that I had studied all of the commit revisions at that time.

I'll re-apply now, record the commit, hope it sticks.