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. * jc/bisect (Fri Mar 23 17:54:03 2007 -0700) 6 commits + make the previous optimization work also on path-limited rev-list --bisect + rev-list --bisect: Fix "halfway" optimization. + t6004: add a bit more path optimization test. + git-rev-list --bisect: optimization + git-rev-list: add --bisect-vars option. + t6002: minor spelling fix. This improves "rev-list --bisect" performance, sometimes significantly, especially in a repository with long lines of single-parent commits. This is only about performance, and as we are already in -rc1, the topic will have to wait 1.5.1. * fl/cvsserver (Mon Mar 19 16:56:01 2007 +0100) 5 commits + cvsserver: Abort if connect to database fails + cvsserver: Make the database backend configurable + cvsserver: Allow to override the configuration per access method + cvsserver: Handle three part keys in git config correctly + cvsserver: Introduce new state variable 'method' This is a beginning of supporting use of different database backends, other than sqlite, with git-cvsserver. Will not be in 'master' until 1.5.1 is done. * js/remote-show-push (Sun Mar 18 21:34:46 2007 +0100) 1 commit + Teach git-remote to list pushed branches. This is a new feature but of very little risk of breaking anything, so I'll merge it to 'master'. * ml/workdir (Sat Mar 17 02:58:55 2007 +0100) 6 commits . git-init: set core.workdir when GIT_WORK_DIR is specified . test GIT_WORK_DIR . test git-rev-parse . core.workdir config variable . introduce GIT_WORK_DIR environment variable . rev-parse: --is-bare-repository option Waiting for a resend without "oops", "ah this is better" iterations, but in no hurry, as it won't be in 'master' until 1.5.1 is done. * jc/fpl (Tue Mar 13 01:57:22 2007 -0700) 1 commit + git-log --first-parent: show only the first parent log This makes viewing topic-heavy style of project history pleasant, at least in my opinion. With a bit of cheering up, I'd merge it to 'master', as it has been cooking in 'next' without causing problems, and is of low-impact kind. But it can wait until 1.5.1 is done. * jc/read-tree-df (Thu Mar 15 23:25:22 2007 -0700) 1 commit . Fix switching to a branch with D/F when current branch has file D. This is unfortunately way premature as it seems to expose other breakages this too-strict safety measure prevents from happening. We need to rethink the whole unpack_trees() business after 1.5.1. * jc/pathattr (Thu Mar 1 01:20:21 2007 -0800) 5 commits . pathattr: allow piping to external program. . pathattr: read from git_config(). . git-show: use pathattr to run "display" . pathattr: path based configuration of various attributes. + convert: add scaffolding for path based selection of conversion routines. Stalled. gitattributes support should be one of the focus in the 1.5.2 cycle. * jc/merge-subtree (Thu Feb 15 16:32:45 2007 -0800) 1 commit - A new merge stragety 'subtree'. * js/fetch-progress (Sun Feb 25 13:13:17 2007 -0800) 1 commit + git-fetch: add --quiet * 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 The above are stalled. - 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