From 8c3450d755d7bb5662ad79f351c50f09ca559e71 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 4 Oct 2017 16:18:43 +0900 Subject: [PATCH] What's cooking (2017/10 #01) --- whats-cooking.txt | 668 ++++++++++++++++++++++++---------------------- 1 file changed, 353 insertions(+), 315 deletions(-) diff --git a/whats-cooking.txt b/whats-cooking.txt index c8015dd0df..09c8f462ec 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 (Sep 2017, #06; Fri, 29) -X-master-at: ea220ee40cbb03a63ebad2be902057bf742492fd -X-next-at: c088eec7b5eaefc58ab32b335cb69cb3d5e2cd78 +Subject: What's cooking in git.git (Oct 2017, #01; Wed, 4) +X-master-at: 8fb8a945bc2dea2bb04249213ad8dacffbfc604f +X-next-at: 6663358d3414aff4d7dac0c6f06cbfcc2cb48ddb -What's cooking in git.git (Sep 2017, #06; Fri, 29) +What's cooking in git.git (Oct 2017, #01; Wed, 4) -------------------------------------------------- Here are the topics that have been cooking. Commits prefixed with @@ -12,6 +12,10 @@ 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. +I wanted to do v2.15-rc0 today but it seems that this has to slip, +with too many topics still in flight in 'next' among which many are +fixes, one is even a fix for a recent regression. + You can find the changes described here in the integration branches of the repositories listed at @@ -20,336 +24,402 @@ of the repositories listed at -------------------------------------------------- [Graduated to "master"] -* hn/typofix (2017-09-22) 1 commit - (merged to 'next' on 2017-09-25 at 489ad60f5b) - + submodule.h: typofix +* ad/doc-markup-fix (2017-09-29) 1 commit + (merged to 'next' on 2017-10-02 at fdf600e8f3) + + doc: correct command formatting + Docfix. -* ic/fix-filter-branch-to-handle-tag-without-tagger (2017-09-22) 4 commits - (merged to 'next' on 2017-09-25 at c7550033df) - + filter-branch: use hash-object instead of mktag - + filter-branch: stash away ref map in a branch - + filter-branch: preserve and restore $GIT_AUTHOR_* and $GIT_COMMITTER_* - + filter-branch: reset $GIT_* before cleaning up - "git filter-branch" cannot reproduce a history with a tag without - the tagger field, which only ancient versions of Git allowed to be - created. This has been corrected. +* bc/rev-parse-parseopt-fix (2017-09-25) 7 commits + (merged to 'next' on 2017-09-26 at f3e013eaa4) + + parse-options: only insert newline in help text if needed + + parse-options: write blank line to correct output stream + + t0040,t1502: Demonstrate parse_options bugs + (merged to 'next' on 2017-09-24 at e479bce0ff) + + git-rebase: don't ignore unexpected command line arguments + + rev-parse parseopt: interpret any whitespace as start of help text + + rev-parse parseopt: do not search help text for flag chars + + t1502: demonstrate rev-parse --parseopt option mis-parsing + Recent versions of "git rev-parse --parseopt" did not parse the + option specification that does not have the optional flags (*=?!) + correctly, which has been corrected. -* ik/userdiff-html-h-element-fix (2017-09-24) 1 commit - (merged to 'next' on 2017-09-25 at e3cbe89672) - + userdiff: fix HTML hunk header regexp - The built-in pattern to detect the "function header" for HTML did - not match

..

elements without any attributes, which has - been fixed. +* bw/git-clang-format (2017-10-01) 1 commit + (merged to 'next' on 2017-10-02 at ee84c89b07) + + clang-format: adjust line break penalties + (this branch is used by sb/git-clang-format.) + Adjust clang-format penalty parameters. -* jc/merge-x-theirs-docfix (2017-09-25) 1 commit - (merged to 'next' on 2017-09-26 at 5a7d954982) - + merge-strategies: avoid implying that "-s theirs" exists - The documentation for '-X