It's now time to pick among the topics that have been cooking in 'next' and 'pu' which ones to start moving to 'master' in what order. I've already kicked one topic out of 'next' as it regresses the http proxy support, but I haven't spent enough time to look at the other topics again closely enough to decide. I was hoping that we could feed a handful of topics every few days to 'master'. I think the following topics (in 'next') are more or less ready: da/difftool-test jn/diffstat-tests jc/commit-hook-authorship tr/maint-word-diff-regex-sticky rs/unpack-trees-leakfix jc/diff-algo-cleanup nd/stream-more zj/test-cred-helper-nicer-prove nl/rebase-i-cheat-sheet jc/maint-clean-nested-worktree-in-subdir jh/notes-merge-in-git-dir-worktree These (in 'next') are "ready" code-wise, but we would need to see the end of the "upstream", "current" or "beginner" discussion: ct/advise-push-default mm/push-default-switch-warning And I think these in 'pu' are ready for 'next': jk/diff-no-rename-empty rs/combine-diff-zero-context-at-the-beginning jc/commit-unedited-template jk/http-backend-keep-committer-ident-env jc/push-upstream-sanity jk/branch-quiet jc/run-hook-env-1 sl/autoconf jb/am-include jc/am-report-3way jc/fmt-merge-msg-people wk/gitweb-snapshot-use-if-modified-since bw/spawn-via-shell-path it/fetch-pack-many-refs jn/debian-customizes-default-editor jk/add-p-skip-conflicts Others not listed here fall into one of the following categories: (1) known to be incomplete; (2) stalled; (3) I simply haven't stared at them long enough; or (4) I don't have strong opinion in the area in general. I'll do a proper "What's cooking" later tonight or tomorrow. -- 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