On Thu, 2006-03-16 at 12:47 -0600, Russ Brown wrote: > We have been using trac for some time now with very few problems. > However, recently the timeline just started crawling along, and is > starting to affect our work. > > Now, two things happened at around about the same time that could have > caused this, so I'd like some ideas on which one it might be and how to > go about resolving it. > > The first problem is that someone in our did a commit that was over a > gigabtye in size. It was full of log files that didn't need to be in VC, > so I dumped and reloaded the repository, replacing the massive checkin > with a dummy revision that just added a blank file. I also had to do the > same for a later revision that was an SVK pull from trunk. Now, > everything works absolutely fine from the point of view of people using > SVN/SVK (though some had to rebuild their depots as they'd already > synced the big change down). So the repository is fine. I'm wondering if > this has anything to do with Trac's revision caching. Is this possible, > and if so would I be able to clear the cache for these revisions and > have Trac re-cache them?
I believe the command is: $ trac-admin resync /your/trac/env -- Rob _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
