From e19a17b3f3ebbd39b4da35fe6edf96f79522a173 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 31 Jan 2018 16:55:41 -0800 Subject: [PATCH] What's cooking (2018/01 #04) --- whats-cooking.txt | 782 ++++++++++++++++++++++------------------------ 1 file changed, 378 insertions(+), 404 deletions(-) diff --git a/whats-cooking.txt b/whats-cooking.txt index 39d7b405e4..a1e0beff9c 100644 --- a/whats-cooking.txt +++ b/whats-cooking.txt @@ -1,10 +1,10 @@ To: git@vger.kernel.org Bcc: lwn@lwn.net -Subject: What's cooking in git.git (Jan 2018, #03; Tue, 23) +Subject: What's cooking in git.git (Jan 2018, #04; Wed, 31) X-master-at: 5be1f00a9a701532232f57958efab4be8c959a29 X-next-at: de0f0111ea2ad3a2b03a378e6272c2ee476a26ed -What's cooking in git.git (Jan 2018, #03; Tue, 23) +What's cooking in git.git (Jan 2018, #04; Wed, 31) -------------------------------------------------- Here are the topics that have been cooking. Commits prefixed with @@ -12,437 +12,208 @@ Here are the topics that have been cooking. Commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. -Many topics in 'next' have been merged to 'master' while others are -tentatively kicked back to 'pu', to give them a chance to be rerolled -if the authors of them wish to do so. +Many new topics appeared and are not yet marked with "Will do what" +labels. Except for some large ones, I think most are already in +good shape, but I'd want to double check by re-reading them. + +I am migrating my build and integration environment to a different +machine; if you notice anything out of ordinary, please let me know +before I decomission and reimage my usual environment ;-) You can find the changes described here in the integration branches of the repositories listed at http://git-blame.blogspot.com/p/git-public-repositories.html --------------------------------------------------- -[Graduated to "master"] - -* ab/commit-m-with-fixup (2017-12-22) 2 commits - (merged to 'next' on 2018-01-11 at 41255c464f) - + commit: add support for --fixup -m"" - + commit doc: document that -c, -C, -F and --fixup with -m error - - "git commit --fixup" did not allow "-m" option to be used - at the same time; allow it to annotate resulting commit with more - text. - - -* ab/doc-cat-file-e-still-shows-errors (2018-01-10) 1 commit - (merged to 'next' on 2018-01-12 at 080bb1d397) - + cat-file doc: document that -e will return some output - - Doc update. - - -* ab/perf-grep-threads (2018-01-04) 1 commit - (merged to 'next' on 2018-01-09 at 91889574fb) - + perf: amend the grep tests to test grep.threads - - More perf tests for threaded grep - - -* as/read-tree-prefix-doc-fix (2018-01-09) 1 commit - (merged to 'next' on 2018-01-12 at 895c72e5c3) - + doc/read-tree: remove obsolete remark - - Doc update. - - -* bw/oidmap-autoinit (2017-12-27) 1 commit - (merged to 'next' on 2018-01-11 at f941e013b4) - + oidmap: ensure map is initialized - - Code clean-up. - - -* cc/codespeed (2018-01-05) 7 commits - (merged to 'next' on 2018-01-09 at 8578089a2b) - + perf/run: read GIT_PERF_REPO_NAME from perf.repoName - + perf/run: learn to send output to codespeed server - + perf/run: learn about perf.codespeedOutput - + perf/run: add conf_opts argument to get_var_from_env_or_config() - + perf/aggregate: implement codespeed JSON output - + perf/aggregate: refactor printing results - + perf/aggregate: fix checking ENV{GIT_PERF_SUBSECTION} - - "perf" test output can be sent to codespeed server. - - -* dk/describe-all-output-fix (2017-12-27) 1 commit - (merged to 'next' on 2017-12-28 at c6254494e3) - + describe: prepend "tags/" when describing tags with embedded name - - An old regression in "git describe --all $annotated_tag^0" has been - fixed. - - -* ew/empty-merge-with-dirty-index (2018-01-09) 1 commit - (merged to 'next' on 2018-01-09 at 6bcda11248) - + Merge branch 'ew/empty-merge-with-dirty-index-maint' into ew/empty-merge-with-dirty-index - (this branch uses ew/empty-merge-with-dirty-index-maint.) - - "git merge -s recursive" did not correctly abort when the index is - dirty, if the merged tree happened to be the same as the current - HEAD, which has been fixed. - - -* jc/merge-symlink-ours-theirs (2018-01-03) 1 commit - (merged to 'next' on 2018-01-05 at 63ebfc45eb) - + merge: teach -Xours/-Xtheirs to symbolic link merge - - "git merge -Xours/-Xtheirs" learned to use our/their version when - resolving a conflicting updates to a symbolic link. - - -* jh/object-filtering (2018-01-08) 1 commit - (merged to 'next' on 2018-01-11 at 56808f6969) - + oidset: don't return value from oidset_init - - Hotfix for a topic already in 'master'. - - -* jk/abort-clone-with-existing-dest (2018-01-03) 4 commits - (merged to 'next' on 2018-01-09 at 3c8e83c3a7) - + clone: do not clean up directories we didn't create - + clone: factor out dir_exists() helper - + t5600: modernize style - + t5600: fix outdated comment about unborn HEAD - - "git clone $there $here" is allowed even when here directory exists - as long as it is an empty directory, but the command incorrectly - removed it upon a failure of the operation. - - -* jm/svn-pushmergeinfo-fix (2017-09-17) 1 commit - (merged to 'next' on 2018-01-05 at 6cb237ea44) - + git-svn: fix svn.pushmergeinfo handling of svn+ssh usernames. - - "git svn dcommit" did not take into account the fact that a - svn+ssh:// URL with a username@ (typically used for pushing) refers - to the same SVN repository without the username@ and failed when - svn.pushmergeinfo option is set. - - -* js/fix-merge-arg-quoting-in-rebase-p (2018-01-05) 1 commit - (merged to 'next' on 2018-01-09 at 91f5601e9c) - + rebase -p: fix quoting when calling `git merge` - - "git rebase -p -X