Christian Boos wrote: > One big reorganization that I think would still be important to do even > before the beta1 is the move of the svn support to tracopt. Now that we > have Git support there, there's no reason to keep svn directly in > trac/versioncontrol (see [2]). I think we can leave around a few > imports for backward compatibility. I created #10712 for that.
IMO the current PyGIT isn't really suitable for a 1.0 release. :) I've started work on a pygit2 based replacement, but am in the middle of an interrupt storm at the moment, keeping me busy elsewhere. I'd be happy if someone else wants to also work with this. It would be very nice to have it included at least as an alternative. Also, while doing this, I've understood just how badly the Git data model fits into Trac's Repository data model. :\ The get_youngest_rev(), previous_rev() and child_revs() Repository operations are very very expensive; they require traversing the entire commit graph! //Peter -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
