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. > > We recommend you make a backup of your existing repository checkout, then make a fresh checkout of the repository in another directory, copy over any changes and commit. Depending on the number of developers on your team and the granularity of change tracking you need for these uncommitted changes, you may need to tune this process for your project. Please coordinate with the other developers on your project team before committing.
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 >
------------------------------------------------------------------------------
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
