From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>, Derrick Stolee <stolee@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Phillip Wood <phillip.wood123@gmail.com>,
Glen Choo <chooglen@google.com>
Subject: Re: Mistakes in the stalled category?
Date: Sat, 15 Jan 2022 11:38:03 -0800 [thread overview]
Message-ID: <xmqqiluk4wo4.fsf@gitster.g> (raw)
In-Reply-To: <xmqqlezh98uj.fsf@gitster.g> (Junio C. Hamano's message of "Fri, 14 Jan 2022 15:49:08 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Elijah Newren <newren@gmail.com> writes:
>
>>> [Stalled]
>>>
>>> * ds/sparse-checkout-requires-per-worktree-config (2021-12-21) 5 commits
>
> [Stalled] being early in the report is primarily a way to remind us
> that an update is overdue.
>
> <1db0f601-4769-15c0-cd58-ecddfa1fc9d5@gmail.com> is what prompted me
> to consider that I can put it on backburner and spend my time on
> other topics.
The pushout of 'seen' I did after -rc1 last night included this
topic again; https://github.com/git/git/actions/runs/1700157728
The CI job triggered Leak Sanitizer in "git init" (the first thing
tests do is to prepare a test repository with working tree, so there
may be other new breakages, but we wouldn't know) and broke CI.
This morning, just to test, I ejected this topic from 'seen' and
pushed it out; https://github.com/git/git/actions/runs/1702373554
As the only difference between these two runs is this topic, it may
be worth looking into locating and fixing new leaks introduced by
it.
Thanks.
next prev parent reply other threads:[~2022-01-15 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 0:48 What's cooking in git.git (Jan 2022, #03; Thu, 13) Junio C Hamano
2022-01-14 4:18 ` Junio C Hamano
2022-01-14 16:27 ` Elijah Newren
2022-01-14 19:47 ` Junio C Hamano
2022-01-14 21:49 ` Elijah Newren
2022-01-14 22:03 ` Junio C Hamano
2022-01-14 22:18 ` Junio C Hamano
2022-01-14 18:12 ` Ævar Arnfjörð Bjarmason
2022-01-17 7:18 ` Patrick Steinhardt
2022-01-14 15:44 ` Mistakes in the stalled category? (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)) Elijah Newren
2022-01-14 23:32 ` Mistakes in the stalled category? Junio C Hamano
2022-01-14 23:49 ` Junio C Hamano
2022-01-15 19:38 ` Junio C Hamano [this message]
2022-01-18 16:11 ` Derrick Stolee
2022-01-14 15:54 ` en/present-despite-skipped & en/remerge-diff (Was: Re: What's cooking in git.git (Jan 2022, #03; Thu, 13)) Elijah Newren
2022-01-14 19:39 ` tb/midx-bitmap-corruption-fix (was: " Taylor Blau
2022-01-15 16:45 ` What's cooking in git.git (Jan 2022, #03; Thu, 13) David Aguilar
2022-01-15 19:15 ` Junio C Hamano
2022-01-16 2:15 ` David Aguilar
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=xmqqiluk4wo4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=chooglen@google.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=phillip.wood123@gmail.com \
--cc=stolee@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).