On 6/4/13, W. Martin Borgert <[email protected]> wrote: > On 2013-06-04 15:58, Grzegorz Sobański wrote: [...] > >> From what I remember reading the code some time ago - it won't. >> Performance problems (and wrong data with cache) are a result of Trac >> version control system being tightly dependant on the SVN model. >> >> GitCachedRepository is using an SVN cache, and its representation >> assumes linear (:D) order of commits. >> >> IMO without huge rewrite of GitCachedRepository and probably some parts >> of the not-cached version no gains can be achieved. > > I see. So there are three options: > - bribe Trac developers to solve the problem (my boss will kill > me for the spendings) > - avoid Git for now (my colleagues will kill me for having to > stay with SVN) > - find an alternative to Trac (I will kill myself for not being > able to work with it) >
That's the situation now , yes ... [...] > > Anyway, from my perspective, Git has a huge momentum and - if I > like it or not - most developers I know, are already using it or > have plans to migrate. If Tracs support for Git does not improve > significantly in the short term, I fear, that people will move > to Gitorious or Gitlab. Both are based on Ruby - no hacking fun > for me :~( > fwiw +1 I do not know whether this suggestion will be a good idea but maybe you could try to create a mercurial mirror (mercurial-git debian package afaicr) and plug it into your Trac instance ... ? -- Regards, Olemis. Apache™ Bloodhound contributor http://issues.apache.org/bloodhound Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
