We've had similar issues with git and concluded it's due to the fact that commits can be out of order with respect to time when they're coming from different branches. I don't remember the exact details but essentially what happened was that e.g. the master branch had a commit at time t1 and after merging a topic branch and pushing it to the trac- git-repo these 'new' commits would come in with timestamps older than t1. Our guess was that the caching mechanism (at least in the git plugin version we're using, I don't have the version number at hand right now) is only looking forward from it's last check-point and therefore does not see the new commits with older timestamps.
All was well (and not too slow) after we disabled the cache. -sas On Dec 10, 10:57 am, Remy Blank <[email protected]> wrote: > Bugs wrote: > > Looks like it is a cache issue. > > Turning off all of trac's caches works, and the timeline is working > > again. > > Well, yes, sure, but the caches are supposed to be working :) > > Maybe you use an older version of the git plugin that doesn't support 0.12? > > -- Remy > > signature.asc > < 1KViewDownload -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
