Righty, so official word is that SF cannot restore that data themselves. Good thing we have external backups.
Dunno how to best restore that data. Should one of the admins (meaning probably me) do it, or should the original commiters re-commit their changes so it correctly tracks as them? Either way, feel free to work with SF's svn again. We know exactly what data is missing - just need to replay it. -- Tino Didriksen On 27 July 2015 at 05:17, Wei En Ng <[email protected]> wrote: > Official email from SourceForge said this: > > > Since commits were made to your repository after our restore point, it > will be necessary > for you to coordinate within your team to ensure these changes are > recommitted. > On Sun, 26 Jul 2015 2:58 pm Tino Didriksen <[email protected]> wrote: > >> https://svn.code.sf.net/p/apertium/svn/ is back up, but it's missing 23 >> revisions worth of data. Last before-crash commit was r61300 >> >> The mirror http://apertium.projectjj.com/svn/apertium-sf-net/ has those >> changesets and they can be browsed at http://apertium.projectjj.com/trac/ >> >> I don't know if SF will eventually recover that data themselves, so wait >> with trying to fix anything until they officially say it's online and all >> they could do. >> >> -- Tino Didriksen >> >
------------------------------------------------------------------------------
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
