From: Patrick Steinhardt <ps@pks.im>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
git@vger.kernel.org, "Arnav Bhate" <bhatearnav@gmail.com>,
"Christian Fredrik Johnsen" <christian@johnsen.no>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
"Elijah Newren" <newren@gmail.com>, "Jeff King" <peff@peff.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Philippe Blain" <levraiphilippeblain@gmail.com>,
"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
"Usman Akinyemi" <usmanakinyemi202@gmail.com>
Subject: Re: "What's cooking" interim report
Date: Fri, 11 Apr 2025 11:28:48 +0200 [thread overview]
Message-ID: <Z_jg0KHpBelL6UXl@pks.im> (raw)
In-Reply-To: <CAOLa=ZRMmEjPoD9-M=XFU37_VoGebYDnH-=nfCyPx0nTvD1=oQ@mail.gmail.com>
On Thu, Apr 10, 2025 at 02:10:28AM -0700, Karthik Nayak wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > Since the issue #02 of this month, a handful of topics have been
> > picked up, a few topics have been replaced by their newer
> > iterations, a topic that is already in 'next' gained an additional
> > commit on top, and a topic got its description extended.
> >
> > --------------------------------------------------
> > Born topics
> >
> > [New Topics]
> >
> > * kn/bundle-dedup-optim (2025-04-08) 2 commits
> > - bundle: fix non-linear performance scaling with refs
> > - t6020: test for duplicate refnames in bundle creation
> >
> > Optimize the code to dedup references recorded in a bundle file.
> >
> > Will merge to 'next'?
> > source: <20250408-488-generating-bundles-with-many-references-has-non-linear-performance-v2-0-0802fc36a23d@gmail.com>
> >
>
> Toon approved/tested the newer version. I'm still wary if some edge-case
> was missed. However the series has added more tests and everything seems
> to be good. So we could merge to next.
I had also reviewed it internally before it was sent to the mailing list
and couldn't spot anything wrong with the current version.
Patrick
next prev parent reply other threads:[~2025-04-11 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 23:10 "What's cooking" interim report Junio C Hamano
2025-04-10 9:10 ` Karthik Nayak
2025-04-11 9:28 ` Patrick Steinhardt [this message]
2025-04-11 9:32 ` Patrick Steinhardt
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=Z_jg0KHpBelL6UXl@pks.im \
--to=ps@pks.im \
--cc=Johannes.Schindelin@gmx.de \
--cc=bhatearnav@gmail.com \
--cc=christian@johnsen.no \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=levraiphilippeblain@gmail.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
--cc=ramsay@ramsayjones.plus.com \
--cc=usmanakinyemi202@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.
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).