On Fri, Jan 29, 2010 at 9:53 AM, yoheeb <[email protected]> wrote: > On Jan 29, 8:41 am, Olemis Lang <[email protected]> wrote: >> > -----Original Message----- >> > From: [email protected] [mailto:[email protected]] >> > On Behalf Of Olemis Lang >> > Sent: Friday, January 29, 2010 8:47 AM >> > To: [email protected] >> > Subject: Re: [Trac] Re: Questions about TracChangeset capabilities >> >> > I am probably (wrong | missing something obvious) but, when talking >> > about Trac & VCS, the solution has to be generic, since the API is >> > designed to connect *ANY* VCS (not just SVN ;o). IMHO the complexities >> > in this case are when something like that is to be implemented >> > (abstracted) for DVCS too, and AFAICR <simpler> functionalities (like >> > copy relationships in TracMercurial ;o) have not been included yet >> > (CMIIW) >> >> > Let's see what the experts have to say anyway ... >> >> > -- >> > Regards, >> >> > Olemis. >> >> > Blog ES:http://simelo-es.blogspot.com/ >> > Blog EN:http://simelo-en.blogspot.com/ >> >> > Featured article: >> > Fixing `setup.py`. Distributing `tracgviz.ig` and `examples`. - >> > http://simelo.hg.sourceforge.net/hgweb/simelo/trac-gviz/rev/275ce6364959 >> >> On Fri, Jan 29, 2010 at 9:22 AM, Prestel, John D. <[email protected]> >> wrote: >> > Sounds like a plug-in to add a few customizations for subversion might >> > be the way to go, then? >> >> Well, if you want to get a page like this one [1]_ but without >> detailed DIFFs shown at the bottom, then I think you should only need >> to change the template or (for better performance ;o) implement a >> clone (plugin) of TracChangesets, remove DIFF calculation, and >> simplify the template anyways. >> >> If you need more advanced features (like I imagined before, but I was >> probably wrong ) then you'll have to add them in a separate plugin >> too, but it would be nice (and helpful) if you could consider Trac VCS >> abstraction API because that would allow to port the same or similar >> functionality to work with multiple VCS (and code could be reused ;o) >> >> .. [1] Changes in xmlrpcplugin/trunk [7485:7000] >> >> (http://trac-hacks.org/changeset?old_path=xmlrpcplugin%2Ftrunk&old=748...) >> > > Why is setting max_diff_bytes and max_diff_files to 0 (or maybe 1, > never tried 0 actually) not sufficient?
Probably performance (which is the main reason why the OP is looking for such a thing, at least considering «Calculating all the diffs can take a LOOOOOOOONG time» , isn't it? ) > you still get the full > changeset summary with the links to the individual diffs. > I've not reviewed the code but that doesn't mean that DIFFs are not calculated in the first place. If they don't then you're right (no differences), otherwise better performance => simplified solution => new plugin (clone ?) ;o) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Microsoft firma acuerdo con la PSF. ¿Python para Visual Studio? - http://feedproxy.google.com/~r/simelo-es/~3/88DyzUrLolE/microsoft-firma-acuerdo-con-la-psf.html -- 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.
