From: luci a. l. d' b. <sf...@gr...> - 2010-07-15 06:59:36
|
+1 to enable (at least to give it a try) On 07/12/2010 10:04 PM, Filipus Klutiero wrote: > Hi, > SourceForge recently upgraded their ViewVC installation to 1.1, which > brought a number of regressions. Most importantly, revision logs now > stop at branch points. For example, trying to find where a bug in > userslib.php on branch 5.x comes from is hard/long. The log is very > short: > http://tikiwiki.svn.sourceforge.net/viewvc/tikiwiki/branches/5.x/lib/userslib.php?view=log > On trunk, the log is better, but nevertheless now stops at our migration > to SVN. Going past that is now very time-consuming (relatively). > > I raised this problem on #sourceforge and they changed back the > behavior, but to discover that this completely broke revision logs, > probably due to a ViewVC 1.1 regression. So SourceForge does not plan to > fix this anymore. Instead, they suggested to enable a Trac instance. > Trac allows the user to choose whether the revision log stops at branch > point or not. It's supposed to be generally better than ViewVC for SVN > browsing too. Can a SF project admin do that? > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Tikiwiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > |