Junio C Hamano <gitster@xxxxxxxxx> writes: > Here are the topics that have been cooking in my tree. Commits > prefixed with '+' are in 'next' (being in 'next' is a sign that a > topic is stable enough to be used and are candidate to be in a > future release). Commits prefixed with '-' are only in 'seen', and > aren't considered "accepted" at all and may be annotated with an URL > to a message that raises issues but they are no means exhaustive. We seem to have too many topics in flight that haven't received adequate reviews. Can contributors divert effort to come up with new patches and topics to reviewing patches already in flight? Here is a summary of topics that are still marked as "Needs review" in the draft of the next issue of "What's cooking report". Needs review. - tb/incremental-midx-part-1 06-07 #19 source: <cover.1717715060.git.me@xxxxxxxxxxxx> - cp/unit-test-reftable-tree 06-13 #5 source: <20240612130217.8877-1-chandrapratap3519@xxxxxxxxx> - cp/unit-test-reftable-pq 06-14 #7 source: <20240614095136.12052-1-chandrapratap3519@xxxxxxxxx> - vd/mktree 06-20 #17 source: <pull.1746.v2.git.1718834285.gitgitgadget@xxxxxxxxx> - en/ort-inner-merge-error-fix 06-20 #7 source: <pull.1748.v2.git.1718766019.gitgitgadget@xxxxxxxxx> - jc/patch-id 06-21 #5 source: <20240621231826.3280338-1-gitster@xxxxxxxxx> There are a few topics that are marked as "Expecting a reroll", but I do not expect they will see an immediate action from their authors if I repeated them here, so I won't do that X-<. Instead, I'll mark the older ones among them as "Will discard". Thanks.
