Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' while commits prefixed with '+' are in 'next'. The topics list the commits in reverse chronological order. * js/reflog (Thu Jan 11 11:47:48 2007 +0100) 1 commit - Teach the revision walker to walk by reflogs with --walk-reflogs It appears to show list of commits with reflog messages, but I am not sure how useful it is until I get used to its output. One question I keep asking reflog has been: When was commit X pushed out as part of 'master'? I have reflog on a tracking branch that I fetch from the public git.git repository immediately after I push into it, so it is a matter of walking the reflog for that branch and see which one is the earliest one that is a descendant of the commit in question. It does not tell me about the mirroring lags, but at least let me keep track of when I pushed something out. * jc/merge-base (Tue Jan 9 02:23:42 2007 -0800) 6 commits - Teach "git-merge-base --check-ancestry" about refs. - git-merge-base: --check-ancestry option + in_merge_bases(): optimization + merge_base(): move traversal into a separate function. + Allow in_merge_bases() to take more than one reference commits. + Make merge-base a built-in. * sp/merge (Thu Dec 28 02:35:17 2006 -0500) 2 commits - Avoid git-fetch in `git-pull .` when possible. + Improve merge performance by avoiding in-index merges. * jc/diff (Mon Dec 25 01:08:50 2006 -0800) 2 commits - test-para: combined diff between HEAD, index and working tree. - para-walk: walk n trees, index and working tree in parallel * jc/explain (Mon Dec 4 19:35:04 2006 -0800) 1 commit - git-explain * jc/3way (Wed Nov 29 18:53:13 2006 -0800) 1 commit + git-merge: preserve and merge local changes when doing fast forward * jc/web (Wed Nov 8 14:54:09 2006 -0800) 1 commit - gitweb: steal loadavg throttle from kernel.org * jc/pickaxe (Sun Nov 5 11:52:43 2006 -0800) 1 commit - blame: --show-stats for easier optimization work. * jc/diff-apply-patch (Fri Sep 22 16:17:58 2006 -0700) 1 commit + git-diff/git-apply: make diff output a bit friendlier to GNU patch (part 2) These are on hold. - 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