Jakub Narebski <jnareb@xxxxxxxxx> writes: >> * jn/gitweb-blame (Thu Aug 6 19:11:52 2009 +0200) 14 commits >> - gitweb: Create links leading to 'blame_incremental' using >> JavaScript >> - gitweb: Incremental blame (proof of concept) >> - gitweb: Add optional "time to generate page" info in footer >> + Revert the four topmost commits from jn/gitweb-blame topic >> + gitweb: Create links leading to 'blame_incremental' using >> JavaScript >> + gitweb: Incremental blame (proof of concept) >> + gitweb: Add optional "time to generate page" info in footer >> + gitweb: Add -partial_query option to href() subroutine >> + gitweb: Use light/dark for class names also in 'blame' view >> + gitweb: Add author initials in 'blame' view, a la "git gui blame" >> + gitweb: Mark commits with no "previous" in 'blame' view >> + gitweb: Use "previous" header of git-blame -p in 'blame' view >> + gitweb: Mark boundary commits in 'blame' view >> + gitweb: Make .error style generic >> >> I haven't picked up Jakub's replacement to the second one from the tip. >> We probably should merge up to "Use light/dark" (aef3768) to 'master' and >> start the rest over. > > That would be good idea. Thanks, will do. > What about 'gitweb: fix variable scoping issue in git_get_projects_list' > latest version of patch, adding (re)declaring $project_maxdepth, > $projectroot as global variables using our? Or are you waiting for > response of our resident Perl expert: Randal L. Schwartz (merlyn)? Not in my queue, but no need to resend --- I can find it. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html