From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: en/merge-tree
Date: Wed, 22 Jun 2022 16:13:41 -0700 [thread overview]
Message-ID: <xmqqk0982swq.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BGGDvZ40TY939fFM0xPZuaogPS+ymfEpc+hv-sJnO8Jcg@mail.gmail.com> (Elijah Newren's message of "Wed, 22 Jun 2022 14:16:28 -0700")
Elijah Newren <newren@gmail.com> writes:
> On Wed, Jun 22, 2022 at 12:41 PM Junio C Hamano <gitster@pobox.com> wrote:
>> [Stalled]
>>
>> * en/merge-tree (2022-02-23) 13 commits
>> ...
> Can you update from "On hold" to "new patchset exists" (new source:
> <pull.1122.v7.git.1655511660.gitgitgadget@gmail.com>) and move it out
> from the stalled section?
As I diverted my attention to the topic for that anyway, it will not
stop at "new patchset exists" but actually would have to be replaced
before getting described in a new issue of the "What's cooking"
report. "Will merge to 'next'?" would be the least the topic would
receive even during the pre-release freeze.
Thanks.
next prev parent reply other threads:[~2022-06-22 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 19:32 What's cooking in git.git (Jun 2022, #07; Wed, 22) Junio C Hamano
2022-06-22 21:16 ` en/merge-tree (Was: Re: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Elijah Newren
2022-06-22 23:13 ` Junio C Hamano [this message]
2022-06-23 10:02 ` Johannes Schindelin
2022-06-23 10:55 ` ab/test-without-templates (was: " Ævar Arnfjörð Bjarmason
2022-06-23 22:12 ` ab/test-without-templates Junio C Hamano
2022-06-27 12:29 ` ab/test-without-templates Ævar Arnfjörð Bjarmason
2022-06-27 16:11 ` ab/test-without-templates Junio C Hamano
2022-06-27 18:23 ` ab/test-without-templates Ævar Arnfjörð Bjarmason
2022-06-23 10:59 ` hx/unpack-streaming (was: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Ævar Arnfjörð Bjarmason
2022-06-23 22:08 ` hx/unpack-streaming Junio C Hamano
2022-06-24 3:12 ` gc/submodule-update (was Re: What's cooking in git.git (Jun 2022, #07; Wed, 22)) Glen Choo
2022-06-24 15:35 ` Junio C Hamano
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=xmqqk0982swq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).