From: Bryan Turner <firstname.lastname@example.org>
To: Junio C Hamano <email@example.com>
Cc: "Ævar Arnfjörð Bjarmason" <firstname.lastname@example.org>,
"Git Users" <email@example.com>,
"Patrick Steinhardt" <firstname.lastname@example.org>
Subject: Re: reference-transaction regression in 2.36.0-rc1
Date: Wed, 13 Apr 2022 15:55:51 -0700 [thread overview]
Message-ID: <CAGyf7-FGdciG+QF8NA_yi=o4B0RVPNiZM4LJZ610cDZzd3AjyQ@mail.gmail.com> (raw)
On Wed, Apr 13, 2022 at 3:48 PM Junio C Hamano <email@example.com> wrote:
> Junio C Hamano <firstname.lastname@example.org> writes:
> > Ævar Arnfjörð Bjarmason <email@example.com> writes:
> >> This does look lik a series regression.
> > Yes.
> >> I haven't had time to bisect this, but I suspect that it'll come down to
> >> something in the 991b4d47f0a (Merge branch
> >> 'ps/avoid-unnecessary-hook-invocation-with-packed-refs', 2022-02-18)
> >> series.
> > With the issue that /var/tmp/.git can cause trouble to those who
> > work in /var/tmp/$USER/playpen being taken reasonably good care of
> > already, it seems this is the issue with the highest priority at
> > this point.
> >> I happen to know that Patrick is OoO until after the final v2.36.0 is
> >> scheduled (but I don't know for sure that we won't spot this thread &
> >> act on it before then).
> Reverting the merge 991b4d47f0a as a whole is an option. It might
> be the safest thing to do, if we do not to want to extend the cycle
> and add a few more -rc releases before the final.
I'm reviewing the changes in the patch series, but while I understand
the visible behavior fairly well the internals of it aren't something
I've spent a lot of time in. Compounding that, I'm down to my final 3
days with Atlassian before I start a new job, so I'm juggling trying
to finish up all my work and/or hand things over to others.
Based on that, I definitely would not want work on 2.36 to hinge on me
getting a patch up. I would _love_ to (finally) contribute something
back to Git, and the community that has helped me so much over the
last 10 years, but I can't say exactly when I'd be able to post
something. There's another developer internally who is also looking at
this, but it's been a number of years since he worked in C.
I guess all that's a long-winded way of saying a revert might be the
more timely option, for decoupling resolving this issue from the 2.36
timeline. That would also mean Patrick would be able to review any fix
that was posted, which seems valuable since he did the original work.
next prev parent reply other threads:[~2022-04-13 22:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:20 reference-transaction regression in 2.36.0-rc1 Bryan Turner
2022-04-12 20:53 ` Bryan Turner
2022-04-13 14:34 ` Ævar Arnfjörð Bjarmason
2022-04-13 16:21 ` René Scharfe
2022-04-13 19:52 ` Junio C Hamano
2022-04-13 22:44 ` Junio C Hamano
2022-04-13 22:55 ` Bryan Turner [this message]
2022-04-13 22:56 ` Junio C Hamano
2022-04-13 23:31 ` Junio C Hamano
2022-04-15 2:37 ` Bryan Turner
2022-04-15 13:27 ` Ævar Arnfjörð Bjarmason
2022-04-15 16:53 ` Junio C Hamano
[not found] ` <CAJDSCnOUQm-doY-xTobPk64oeiSsTd+vSFzsb_cz9BLORAxXGA@mail.gmail.com>
2022-04-27 11:05 ` Patrick Steinhardt
[not found] ` <CAJDSCnM767fdo6qy085jc9sqezvbBqDD4ikXz1y5tHEjSYED2A@mail.gmail.com>
2022-05-02 11:12 ` Patrick Steinhardt
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.