I've merged a handful of topics to 'next', and hoping that many of them can be merged to 'master' before I'll go offline for a few weeks starting on the week #7 of the cycle (starting Nov 9th). As I hate sending out the whole text back to back (the last one was issued on the last Friday), here is an abbreviated update for the "What's cooking" report, highlighting those topics that I want to see in 'master' by the end of the week #6 (Nov 8th). Thanks. * kn/for-each-branch (2015-10-30) 1 commit (merged to 'next' on 2015-11-01 at 4249dc9) + ref-filter: fallback on alphabetical comparison Using the timestamp based criteria in "git branch --sort" did not tiebreak branches that point at commits with the same timestamp (or the same commit), making the resulting output unstable. Will merge to 'master'. * jc/mailinfo-lib (2015-11-01) 1 commit (merged to 'next' on 2015-11-01 at 3ecaa28) + mailinfo: fix passing wrong address to git_mailinfo_config Hotfix for a topic already in 'master'. Will merge to 'master'. * sb/submodule-parallel-fetch (2015-10-21) 14 commits (merged to 'next' on 2015-10-23 at 8f04bbd) + run-command: fix missing output from late callbacks + test-run-command: increase test coverage + test-run-command: test for gracefully aborting + run-command: initialize the shutdown flag + run-command: clear leftover state from child_process structure + run-command: fix early shutdown (merged to 'next' on 2015-10-15 at df63590) + submodules: allow parallel fetching, add tests and documentation + fetch_populated_submodules: use new parallel job processing + run-command: add an asynchronous parallel child processor + sigchain: add command to pop all common signals + strbuf: add strbuf_read_once to read without blocking + xread_nonblock: add functionality to read from fds without blocking + xread: poll on non blocking fds + submodule.c: write "Fetching submodule <foo>" to stderr (this branch is used by rs/daemon-leak-fix and sb/submodule-parallel-update.) Add a framework to spawn a group of processes in parallel, and use it to run "git fetch --recurse-submodules" in parallel. Will merge to 'master'. * rs/daemon-leak-fix (2015-10-31) 3 commits (merged to 'next' on 2015-11-01 at 9b6c8f9) + daemon: plug memory leak + run-command: export child_process_clear() + run-command: name the cleanup function child_process_clear() (this branch is used by sb/submodule-parallel-update; uses sb/submodule-parallel-fetch.) "git daemon" uses "run_command()" without "finish_command()", so it needs to release resources itself, which it forgot to do. Will merge to 'master'. * rs/wt-status-detached-branch-fix (2015-11-01) 5 commits (merged to 'next' on 2015-11-01 at cb23615) + wt-status: use skip_prefix() to get rid of magic string length constants + wt-status: don't skip a magical number of characters blindly + wt-status: avoid building bogus branch name with detached HEAD + wt-status: exit early using goto in wt_shortstatus_print_tracking() + t7060: add test for status --branch on a detached HEAD "git status --branch --short" accessed beyond the constant string "HEAD", which has been corrected. Will merge to 'master'. * da/difftool (2015-10-29) 1 commit (merged to 'next' on 2015-11-01 at 4e5ab33) + difftool: ignore symbolic links in use_wt_file The code to prepare the working tree side of temporary directory for the "dir-diff" feature forgot that symbolic links need not be copied (or symlinked) to the temporary area, as the code already special cases and overwrites them. Besides, it was wrong to try computing the object name of the target of symbolic link, which may not even exist or may be a directory. Will merge to 'master'. * jk/initialization-fix-to-add-submodule-odb (2015-10-28) 1 commit (merged to 'next' on 2015-11-01 at da94b97) + add_submodule_odb: initialize alt_odb list earlier We peek objects from submodule's object store by linking it to the list of alternate object databases, but the code to do so forgot to correctly initialize the list. Will merge to 'master'. -- 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