On Tue, Jan 10, 2023 at 01:22:13PM -0800, Paul Wagland wrote:
> Did this patch ever end up getting merged in? I am seeing the problem again
> in my repo with git 2.39.0, so was just wondering if this managed to make
> it upstream
[...]
I think it did not manage to come through yet [1].
You
Hi Mathias,
Did this patch ever end up getting merged in? I am seeing the problem again
in my repo with git 2.39.0, so was just wondering if this managed to make
it upstream
Cheers,
Paul
On Wednesday, October 19, 2022 at 9:10:55 AM UTC+2 Paul Wagland wrote:
> Thanks Mathias!
>
> This patch
Thanks Mathias!
This patch seems to have gained some traction as well, so I am glad that my
pain lead to some improvement :-)
Cheers,
Paul
On Tuesday, October 18, 2022 at 5:42:47 PM UTC+2 Mathias Rav wrote:
> On Monday, October 17, 2022 at 8:27:44 PM UTC+2 Paul wrote:
>
>> Based on the above,
On Monday, October 17, 2022 at 8:27:44 PM UTC+2 Paul wrote:
> Based on the above, I contacted the git list, and got a response from Jeff:
> > It sounds like there's a resolve-undo extension in your index
> that references that blob, but the blob was removed from the
> repository (probably by a
Hi Mathias,
Based on the above, I contacted the git list, and got a response from Jeff:
> It sounds like there's a resolve-undo extension in your index
that references that blob, but the blob was removed from the
repository (probably by a gc prior to 5a5ea141e7, which was trying to
prevent
Hi Mathias,
I have not figured out a solution yet, I have just pinned my git to 2.37.1
and continued on, I haven't circled back to look at this yet.
In the meantime 2.38.0 is also released, and that has the same issue for me.
I did some further testing based on your feedback, and building git
On Friday, September 16, 2022 at 12:35:24 AM UTC+2 Paul wrote:
> However, when I upgrade to git 2.37.2, or 2.37.3, git gc suddenly starts
> to fail:
> fatal: unable to read 1d0f34d1c4314efcff527847755e4ccc77d44fb6
>
> fatal: failed to run repack
> How can I work out what reference is causing