Junio C Hamano <gitster@xxxxxxxxx> writes: > with '-' are only in 'pu' while commits prefixed with '+' are > in 'next'. The ones marked with '.' do not appear in any of the branches, > but I am still holding onto them. > > The topics list the commits in reverse chronological order. The topics > meant to be merged to the maintenance series have "maint-" in their names. > > ---------------------------------------------------------------- > [Actively cooking] > > * mk/gitweb-feature (Mon Dec 15 22:16:19 2008 -0800) 1 commit > - gitweb: unify boolean feature subroutines Nice thing from what I remember (I assume it is last incantation?). > * jn/gitweb-blame (Thu Dec 11 01:33:29 2008 +0100) 3 commits > - gitweb: cache $parent_commit info in git_blame() > - gitweb: A bit of code cleanup in git_blame() > - gitweb: Move 'lineno' id from link to row element in git_blame > > Jakub seemed to feel they are not yet ready. This is, I think, ready. It is incremental AJAX-y blame in gitweb that is not yet ready; this is simple cleanup and performance improvement. > * 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 I think this needs a bit more cooking; with one more commit I think you can have categories within requested sort order, and not always sorted alphabetically. > * 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 I think it is ready, or almost ready. I'll try to review this series within a week. Feel free to prod me if I forget. P.S. BTW. what is the status on using parse_options among git commands? -- Jakub Narebski Poland ShadeHawk on #git -- 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
