Things seem to be returning to normal now. If you're still seeing this CVS error, let us know and we'll look into it for you.
David > Is this: > > cvs commit: Up-to-date check failed for > `src/chrome/content/tamperdata.js' > cvs [commit aborted]: correct above errors first! > > part of the same set of problems? > > > Will it go away by itself, or do I need to do something? > > I'm able to commit some files, but not an entire directory. > > Adam > > On 30/11/05, David Boswell <[EMAIL PROTECTED]> wrote: > > > I don't want to whinge, but when is mozdev getting their new > > > server? > > > > Soon. We'll post more details as soon as we can. Hardware has > been > > ordered though. > > > > Unfortunately the site got hit by the Firefox release and this > added to > > the existing performance problems. We are devoting all available > > resources to make the site perform better and things should be > running > > smoothly again in the near future. > > > > I blame it all on mozilla.org. If more than 10% of people weren't > > using Firefox, we wouldn't be in this mess :) > > > > David > > _______________________________________________ > > Project_owners mailing list > > [email protected] > > http://mozdev.org/mailman/listinfo/project_owners > > > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
