From: Junio C Hamano <gitster@pobox.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: git@vger.kernel.org, "Eric W. Biederman" <ebiederm@gmail.com>
Subject: Re: What's cooking in git.git (Oct 2023, #01; Mon, 2)
Date: Wed, 04 Oct 2023 09:28:00 -0700 [thread overview]
Message-ID: <xmqq5y3ms67j.fsf@gitster.g> (raw)
In-Reply-To: <875y3n4207.fsf@email.froward.int.ebiederm.org> (Eric W. Biederman's message of "Tue, 03 Oct 2023 20:20:24 -0500")
"Eric W. Biederman" <ebiederm@xmission.com> writes:
> I pushed v2 out precisely because it contains fixes that should have
> fixed all of the CI breakages.
>
> I am not really familiar with github but looking at the recent CI runs
> it appears since v2 landed the seen branch has been building cleanly.
https://github.com/git/git/actions/runs/6398848314 shows the CI run
with seen at 7052c9b and it seems it does have the
eb/hash-transition topic in it.
> I just don't want people to avoid reviewing it because it is that huge
> patchset that causes problems in seen.
Certainly.
I have seen people review patches that do not even compile, though,
so "problems in seen" may not be that much of an issue, compared to
how intimidating the large series looks like.
Thanks.
prev parent reply other threads:[~2023-10-04 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 0:30 What's cooking in git.git (Oct 2023, #01; Mon, 2) Junio C Hamano
2023-10-03 7:01 ` Sergey Organov
2023-10-03 16:33 ` Junio C Hamano
2023-10-03 17:59 ` Sergey Organov
2023-10-04 8:20 ` Junio C Hamano
2023-10-04 11:18 ` Sergey Organov
2023-10-05 10:25 ` Junio C Hamano
2023-10-05 20:59 ` Sergey Organov
2023-10-05 21:47 ` Junio C Hamano
2023-10-06 18:02 ` Sergey Organov
2023-10-04 1:20 ` Eric W. Biederman
2023-10-04 16:28 ` 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=xmqq5y3ms67j.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ebiederm@gmail.com \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
/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).