So, there are new versions out. However, I'd suggest not using the tip version; pull r5, if you use it at all. There's a problem with how Trac change log and ditz log events are identified, and a more serious problem stemming from the fact that the Trac change log time stamps are not controllable through XMLRPC, which can lead to ditz issue log events being duplicated. r5 doesn't have this problem, because it's ditz -> Trac syncing is limited to creating tickets, milestones, and components -- it doesn't sync the change logs (in that direction) yet.
--- SER
_______________________________________________ ditz-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ditz-talk
