Jakub Narebski <jnareb@xxxxxxxxx> writes: >> ---------------------------------------------------------------- >> [Actively cooking] >> >> * sc/gitweb-category (Fri Dec 12 00:45:12 2008 +0100) 3 commits >> - gitweb: Optional grouping of projects by category >> - gitweb: Split git_project_list_body in two functions >> - gitweb: Modularized git_get_project_description to be more generic > > This I think needs some further cooking. I guess with addition of one > more patch to series categories could be sorted together with projects > they contain, and not always have to be in fixed ordering. These should be moved to the Stalled category; nobody seems to be discussing improvements and sending updates to the series as far as I recall. >> * gb/gitweb-patch (Thu Dec 18 08:13:19 2008 +0100) 4 commits >> - gitweb: link to patch(es) view in commit(diff) and (short)log view >> - gitweb: add patches view >> - gitweb: change call pattern for git_commitdiff >> - gitweb: add patch view > > If I remember correctly the only point of discussion is calling > convention for git_commitdiff, and whether 'patches' view should > (re)use git_commitdiff or use its own subroutine. Thanks; I take it that it is basically usable, useful and can be incrementally improved in 'next'? -- 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
