From: Justin Tobler <jltobler@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, ps@pks.im, peff@peff.net,
luca.stefani.ge1@gmail.com
Subject: Re: [PATCH] object-file: avoid ODB transaction when not writing objects
Date: Tue, 7 Apr 2026 17:41:12 -0500 [thread overview]
Message-ID: <adWGjWNTXlR-glgt@denethor> (raw)
In-Reply-To: <xmqq7bqi2yux.fsf@gitster.g>
On 26/04/07 03:24PM, Junio C Hamano wrote:
> Justin Tobler <jltobler@gmail.com> writes:
>
> > On 26/04/07 02:53PM, Junio C Hamano wrote:
> >> Junio C Hamano <gitster@pobox.com> writes:
> >>
> >> > I'd appreciate it if you can give your eyeballs to the attached to
> >> > see if that is how you would fixed the bug in the original context
> >> > of v2.52 track. If everything looks OK, then there is no need to
> >> > spend time backporting on your side. We have everything necessary.
> >>
> >> Another thing. Your jt/odb-transaction-write topic (in 'seen')
> >> already addresses this issue, so we may merge this single patch down
> >> to 'next' and 'master' first, but the merge that brings in the topic
> >> can just supersede this patch, perhaps keeping the test added to
> >> t1517.
> >
> > That would work :)
> >
> >> Do I understand correctly? The t1517 part of the patch, when
> >> applied to 'seen', does indicate that the problem is not there.
> >
> > Yes, that is correct. The jt/odb-transaction-write topic indeed already
> > fixes this issue. The patch here is just a slimmed down version of a
> > patch from that series.
> >
> > I can also send a follow up version for the topic built on top of this
> > patch if that would be preferred. Otherwise, replacing the patch with
> > the original topic and keeping the test as you suggested would work just
> > fine.
>
> OK. I think I am almost done preparing for tonight's pushout, so
> please double check, and complain if you see something that is
> questionable, when it happens. It probably will happen in 2 hours
> or so.
Thanks, I'll make sure to double check.
I'm not sure if you already included an update for the test per Peff's
comments, but if not we can do something like below. If you would like I
can send another version with it included too.
Thanks,
-Justin
--- >8 ---
diff --git a/t/t1517-outside-repo.sh b/t/t1517-outside-repo.sh
index c1dbc6359a..e1d35170de 100755
--- a/t/t1517-outside-repo.sh
+++ b/t/t1517-outside-repo.sh
@@ -93,12 +93,12 @@ test_expect_success 'diff outside repository' '
test_cmp expect actual
'
-test_expect_success 'diff files exceeding bigFileThreshold outside repository' '
- cd non-repo &&
- echo foo >foo &&
- echo bar >bar &&
- test_must_fail git -c core.bigFileThreshold=1 diff -- foo bar >actual &&
- test_grep "diff --git a/foo b/bar" actual
+test_expect_success 'hash object exceeding bigFileThreshold outside repository' '
+ (
+ cd non-repo &&
+ echo foo >foo &&
+ git -c core.bigFileThreshold=1 hash-object --stdin <foo
+ )
'
test_expect_success 'stripspace outside repository' '
next prev parent reply other threads:[~2026-04-07 22:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 20:17 [PATCH] object-file: avoid ODB transaction when not writing objects Justin Tobler
2026-04-07 21:18 ` Junio C Hamano
2026-04-07 21:29 ` Jeff King
2026-04-07 21:43 ` Junio C Hamano
2026-04-07 21:43 ` Justin Tobler
2026-04-07 21:53 ` Junio C Hamano
2026-04-07 22:08 ` Justin Tobler
2026-04-07 22:24 ` Junio C Hamano
2026-04-07 22:41 ` Justin Tobler [this message]
2026-04-08 0:42 ` Junio C Hamano
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=adWGjWNTXlR-glgt@denethor \
--to=jltobler@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luca.stefani.ge1@gmail.com \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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