{"thread":{"id":"59148","subject":"A summary of in-flight topics","startedAt":"2023-01-24T22:30:18Z","lastAt":"2023-01-25T17:13:25Z","messageCount":3,"participants":["Junio C Hamano","Elijah Newren"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"471003","messageId":"xmqq7cxbftvu.fsf@gitster.g","threadId":"59148","inReplyTo":null,"subject":"A summary of in-flight topics","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-01-24T22:30:13Z","receivedAt":"2023-01-24T22:30:18Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"I hate to send out new issues of the \"What's cooking\" report too\noften, but we have too many in-flight topics that are not getting\ntraction they may deserve, so let me send out a summary of the\ntopics listed in the draft I have for the next issue of it.\n\nThose that are marked as \"will merge to 'master'\" won't be merged\nimmediately; they usually spend at least 1 calendar week in 'next'\n(the second date on the line for each topic is the date they were\nmerged to 'next').\n\n--------------------------------------------------\n\nExpecting a (hopefully final) reroll.\n - ms/send-email-feed-header-to-validate-hook 01-19 #2\n - cb/checkout-same-branch-twice 01-20 #1\n - rj/avoid-switching-to-already-used-branch 01-22 #3\n\nExpecting a hopefully minor and final reroll.\n - ab/avoid-losing-exit-codes-in-tests 12-20 #6\n\nExpecting a reroll.\n - tl/notes--blankline 11-09 #5\n - ab/tag-object-type-errors 11-22 #5\n - ab/config-multi-and-nonbool 11-27 #9\n - cb/grep-fallback-failing-jit 12-17 #1\n - ja/worktree-orphan 01-13 #4\n - tc/cat-file-z-use-cquote 01-16 #1\n - rj/branch-unborn-in-other-worktrees 01-19 #3\n\nMay want to discard. Breaking compatibility does not seem worth it.\n - so/diff-merges-more 12-18 #5\n\nMay want to discard. Its jaggy edges may be a bit too sharp.\n - cc/filtered-repack 12-25 #3\n\nNeeds review on the updated round.\n - ed/fsmonitor-inotify 12-13 #6\n\nNeeds review.\n - jc/spell-id-in-both-caps-in-message-id 12-17 #1\n - ad/test-record-count-when-harness-is-in-use 12-25 #1\n - cw/submodule-status-in-parallel 01-17 #6\n - ab/sequencer-unleak 01-18 #8\n - ab/various-leak-fixes 01-18 #19\n\nUndecided\n - rs/tree-parse-mode-overflow-check 01-21 #1\n - rj/bisect-already-used-branch 01-22 #1\n - ab/hook-api-with-stdin 01-23 #5\n - ds/bundle-uri-5 01-23 #10\n\nWaiting for review response.\n - mc/switch-advice 11-09 #1\n - js/range-diff-mbox 11-23 #1\n\nWill merge to 'master'.\n + ab/cache-api-cleanup-users 01-17/01-18 #3\n + sa/cat-file-mailmap--batch-check 01-18/01-18 #1\n + km/send-email-with-v-reroll-count 11-27/01-19 #1\n + pb/branch-advice-recurse-submodules 01-18/01-19 #1\n + jc/doc-branch-update-checked-out-branch 01-18/01-19 #1\n + cb/grep-pcre-ucp 01-18/01-19 #1\n + jk/hash-object-literally-fd-leak 01-19/01-19 #1\n + cw/fetch-remote-group-with-duplication 01-19/01-20 #1\n + jc/doc-checkout-b 01-19/01-23 #1\n + po/pretty-format-columns-doc 01-19/01-23 #5\n + jk/hash-object-fsck 01-19/01-23 #7\n + en/rebase-update-refs-needs-merge-backend 01-22/01-23 #9\n + tb/t0003-invoke-dd-more-portably 01-22/01-23 #1\n + jc/attr-doc-fix 01-22/01-24 #1\n + ar/markup-em-dash 01-23/01-24 #1\n\nWill merge to 'next'.\n - mc/credential-helper-auth-headers 01-20 #12\n\nWill merge to 'next'?\n - en/ls-files-doc-update 01-13 #4\n - as/ssh-signing-improve-key-missing-error 01-24 #1\n"},{"id":"471023","messageId":"CABPp-BH0LwHvN_bXp0BpekQ+f+15KNXQRzf5LCn3_BhcPzB-3A@mail.gmail.com","threadId":"59148","inReplyTo":"xmqq7cxbftvu.fsf@gitster.g","subject":"Re: A summary of in-flight topics","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2023-01-25T16:05:57Z","receivedAt":"2023-01-25T16:06:23Z","isPatch":false,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Tue, Jan 24, 2023 at 2:37 PM Junio C Hamano wrote:\n[...]\n> - ab/sequencer-unleak 01-18 #8\n\nPerhaps move to \"Expecting a hopefully minor and final reroll\"? See\ne.g. https://lore.kernel.org/git/xmqqedry17r4.fsf@gitster.g/ where you\ncommented on Phillip's approving the code changes but wanting a number\nof commit message cleanups and fixes. Ævar did send a v3, and Phillip\ncommented on two of those patches, suggesting one could still use some\ncommit message cleanups.\n\n> - ab/various-leak-fixes 01-18 #19\n\nIsn't this already merged as 9ea1378d04 (\"Merge branch\n'ab/various-leak-fixes'\", 2022-12-14) ? Why does it appear under\n\"needing review\"? (I started reviewing, and while looking at the\nexisting code noted it already had the relevant changes, then went\ndigging and found it was merged...)\n\n> Will merge to 'master'.\n> + en/rebase-update-refs-needs-merge-backend 01-22/01-23 #9\n\nI sent out a v5 since you sent this email, to include some final\nchanges Phillip was suggesting. He seems happy with those\n(https://lore.kernel.org/git/94deff87-a4a0-e937-7549-3e5348361a12@dunelm.org.uk/),\nso I agree it can merge down, but please use v5 instead of v4.\n\n> Will merge to 'next'?\n> - en/ls-files-doc-update 01-13 #4\n\nI'm in favor, but self votes don't count so...\n"},{"id":"471028","messageId":"xmqqzga6edx4.fsf@gitster.g","threadId":"59148","inReplyTo":"CABPp-BH0LwHvN_bXp0BpekQ+f+15KNXQRzf5LCn3_BhcPzB-3A@mail.gmail.com","subject":"Re: A summary of in-flight topics","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-01-25T17:12:39Z","receivedAt":"2023-01-25T17:13:25Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Elijah Newren writes:\n\n> On Tue, Jan 24, 2023 at 2:37 PM Junio C Hamano wrote:\n> [...]\n>> - ab/sequencer-unleak 01-18 #8\n>\n> Perhaps move to \"Expecting a hopefully minor and final reroll\"? See\n> e.g. https://lore.kernel.org/git/xmqqedry17r4.fsf@gitster.g/ where you\n> commented on Phillip's approving the code changes but wanting a number\n> of commit message cleanups and fixes. Ævar did send a v3, and Phillip\n> commented on two of those patches, suggesting one could still use some\n> commit message cleanups.\n\nThanks, you're right.\n\n>> - ab/various-leak-fixes 01-18 #19\n>\n> Isn't this already merged as 9ea1378d04 (\"Merge branch\n> 'ab/various-leak-fixes'\", 2022-12-14)?\n\nThe cover letter of its first iteration says\n\n This is a follow-up to the ab/various-leak-fixes topic merged in\n 9ea1378d046 (Merge branch 'ab/various-leak-fixes', 2022-12-14). Like\n that topic this is mixed collection of various leak fixes, all of\n which should be simple to review & reason about.\n\nUnfortunately the text does not appear in the cover for the\nlatest iteration, but that is how the topic name was reused.\n\nTHanks.\n"}]}