From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2021, #03; Wed, 10)
Date: Wed, 10 Mar 2021 22:08:58 -0800 [thread overview]
Message-ID: <xmqq5z1yfchx.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BHxj8jS62mVH4qgmoh1v48ciz8CRswz3+twSnuxUo7Rmw@mail.gmail.com> (Elijah Newren's message of "Wed, 10 Mar 2021 20:49:56 -0800")
Elijah Newren <newren@gmail.com> writes:
> On Wed, Mar 10, 2021 at 7:05 PM Junio C Hamano <gitster@pobox.com> wrote:
>> --------------------------------------------------
>> [New Topics]
> ...
>
> Is there any reason the topics at
>
> https://lore.kernel.org/git/pull.845.git.1614484707.gitgitgadget@gmail.com/T/#t
>
> and
>
> https://lore.kernel.org/git/pull.973.git.git.1614905738.gitgitgadget@gmail.com/T/#t
>
> haven't been picked up yet?
While we are in pre-release freeze, I'd refrain from picking up a
brand new code with nontrivial complexity that is under discusion on
the list (because I know I cannot spare enough bandwidth to keep up
with the discussion and picking up an early iteration, and risking
to merge it down without refreshing it with a newer iteration by
mistake, is not a good tradeoff), while I am busy dealing with
prerelease issues. I do use the spare time to follow discussions on
topics that are already in tree and possibly replace them with their
newer rounds, and also new code that are of less importance and
easier to reason about.
next prev parent reply other threads:[~2021-03-11 6:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:01 What's cooking in git.git (Mar 2021, #03; Wed, 10) Junio C Hamano
2021-03-11 4:49 ` Elijah Newren
2021-03-11 6:08 ` Junio C Hamano [this message]
2021-03-11 5:20 ` ZheNing Hu
2021-03-11 5:28 ` Junio C Hamano
2021-03-11 6:18 ` ZheNing Hu
2021-03-11 11:44 ` Ævar Arnfjörð Bjarmason
2021-03-11 13:01 ` Han-Wen Nienhuys
2021-03-11 18:12 ` Junio C Hamano
2021-03-11 16:17 ` Elijah Newren
2021-03-11 18:27 ` Junio C Hamano
2021-03-11 19:17 ` Jeff King
2021-03-12 7:10 ` Junio C Hamano
2021-03-11 19:13 ` René Scharfe.
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5z1yfchx.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).