public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Jun 2024, #08; Mon, 24)
Date: Tue, 25 Jun 2024 21:37:00 -0700	[thread overview]
Message-ID: <xmqq4j9g8glv.fsf@gitster.g> (raw)
In-Reply-To: <xmqqbk3pakol.fsf@gitster.g> (Junio C. Hamano's message of "Mon, 24 Jun 2024 18:13:46 -0700")

Junio C Hamano <gitster@pobox•com> 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@ttaylorr•com>
 - cp/unit-test-reftable-tree                                   06-13          #5
 source: <20240612130217.8877-1-chandrapratap3519@gmail•com>
 - cp/unit-test-reftable-pq                                     06-14          #7
 source: <20240614095136.12052-1-chandrapratap3519@gmail•com>
 - vd/mktree                                                    06-20         #17
 source: <pull.1746.v2.git.1718834285.gitgitgadget@gmail•com>
 - en/ort-inner-merge-error-fix                                 06-20          #7
 source: <pull.1748.v2.git.1718766019.gitgitgadget@gmail•com>
 - jc/patch-id                                                  06-21          #5
 source: <20240621231826.3280338-1-gitster@pobox•com>

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.

      parent reply	other threads:[~2024-06-26  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  1:13 What's cooking in git.git (Jun 2024, #08; Mon, 24) Junio C Hamano
2024-06-25 17:02 ` Rubén Justo
2024-06-26  4:37 ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq4j9g8glv.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox