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/rebase (Mon Jun 25 01:11:14 2007 +0100) 2 commits + Teach rebase an interactive mode + Move the pick_author code to git-sh-setup Will merge. * rs/diff (Mon Jun 25 00:23:34 2007 +0200) 2 commits + diff: round down similarity index + diffcore-rename: don't change similarity index based on basename equality Will merge. * lt/run (Sun Jun 24 10:29:33 2007 -0700) 2 commits + Check for IO errors after running a command + Clean up internal command handling Will merge. * ew/svn (Wed Jun 13 02:23:28 2007 -0700) 1 commit + git-svn: allow dcommit to retain local merge information Haven't heard major breakage report, so hopefully can merge by the end of the month. * mk/svn (Fri Jun 22 11:15:03 2007 +0200) 1 commit - git-svn: honor ~/.subversion/ client cert file settings. Waiting for ACK from git-svn people. * ml/worktree (Fri Jun 8 22:57:55 2007 +0200) 9 commits + make git barf when an alias changes environment variables + setup_git_directory: fix segfault if repository is found in cwd + test GIT_WORK_TREE + extend rev-parse test for --is-inside-work-tree + Use new semantics of is_bare/inside_git_dir/inside_work_tree + introduce GIT_WORK_TREE to specify the work tree + test git rev-parse + rev-parse: introduce --is-bare-repository + rev-parse: document --is-inside-git-dir * ei/worktree+filter (Wed Jun 6 09:16:56 2007 +0200) 9 commits + filter-branch: always export GIT_DIR if it is set I've been resisting these due to the size of the series, but I think the definition of is-bare is a bit saner than what we have in 'master', and I think it is the right direction in the longer term. HOWEVER, I am not sure about the implementation and corner cases, e.g. what should it do in receive-pack? You cannot rely on user setting GIT_WORK_TREE environment -- rather, receive-pack is responsible for setting up a sane environment for other commands to work in. * jc/quote (Sun Jun 24 15:11:24 2007 -0700) 1 commit + Add core.quotepath configuration variable. This will get rid of "Why is my UTF-8 pathnames are munged" complaints. Will wait for a while, maybe merge after 1.5.3. I believe the output from this is still readable by an unpatched git-apply, but I would want to be absolutely sure. * jo/init (Thu Jun 7 07:50:30 2007 -0500) 2 commits - Quiet the output from git-init when cloning, if requested. - Add an option to quiet git-init. I am not very much interested in this but I do not have any strong or otherwise feeling against it either. * dh/repack (Fri May 25 14:40:24 2007 -0700) 1 commit - Enhance unpack-objects for live repo and large objects * jc/blame (Fri Apr 20 16:25:50 2007 -0700) 4 commits - blame: show log as it goes - git-blame: optimize get_origin() from linear search to hash- lookup. - git-blame: pass "struct scoreboard *" pointers around. - blame: lift structure definitions up * 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 Backburnered. - 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
