From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2024, #01; Mon, 3)
Date: Tue, 4 Jun 2024 10:06:40 +0200 [thread overview]
Message-ID: <Zl7LEHFq4FcXMvGd@framework> (raw)
In-Reply-To: <xmqqo78h1bdg.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]
On Mon, Jun 03, 2024 at 11:16:11PM -0700, Junio C Hamano wrote:
> * jk/sparse-leakfix (2024-05-31) 14 commits
> - sparse-checkout: free duplicate hashmap entries
> - sparse-checkout: free string list after displaying
> - sparse-checkout: free pattern list in sparse_checkout_list()
> - sparse-checkout: free sparse_filename after use
> - sparse-checkout: refactor temporary sparse_checkout_patterns
> - sparse-checkout: always free "line" strbuf after reading input
> - sparse-checkout: reuse --stdin buffer when reading patterns
> - dir.c: always copy input to add_pattern()
> - dir.c: free removed sparse-pattern hashmap entries
> - sparse-checkout: clear patterns when init() sees existing sparse file
> - dir.c: free strings in sparse cone pattern hashmaps
> - sparse-checkout: pass string literals directly to add_pattern()
> - sparse-checkout: free string list in write_cone_to_file()
> - Merge branch 'jk/leakfixes' into jk/sparse-leakfix
> (this branch uses jk/leakfixes and ps/leakfixes.)
>
> Many memory leaks in the sparse-checkout code paths have been
> plugged.
>
> Will merge to 'next'?
> source: <20240531112433.GA428583@coredump.intra.peff.net>
I've left a couple of comments on that patch series this morning.
> * ps/ref-storage-migration (2024-06-03) 14 commits
> - builtin/refs: new command to migrate ref storage formats
> - refs: implement logic to migrate between ref storage formats
> - refs: implement removal of ref storages
> - worktree: don't store main worktree twice
> - reftable: inline `merged_table_release()`
> - refs/files: fix NULL pointer deref when releasing ref store
> - refs/files: extract function to iterate through root refs
> - refs/files: refactor `add_pseudoref_and_head_entries()`
> - refs: allow to skip creation of reflog entries
> - refs: pass storage format to `ref_store_init()` explicitly
> - refs: convert ref storage format to an enum
> - setup: unset ref storage when reinitializing repository version
> - Merge branch 'ps/pseudo-ref-terminology' into ps/ref-storage-migration
> - Merge branch 'ps/refs-without-the-repository-updates' into ps/ref-storage-migration
>
> Allow migrating a repository that uses the files backend for its
> ref storage to use the reftable backend, with limitations.
>
> Will merge to 'next'?
> source: <cover.1717402363.git.ps@pks.im>
This one is ready to go from my point of view.
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-04 8:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:16 What's cooking in git.git (Jun 2024, #01; Mon, 3) Junio C Hamano
2024-06-04 8:06 ` Patrick Steinhardt [this message]
2024-06-04 8:07 ` Karthik Nayak
2024-06-04 18:31 ` Junio C Hamano
2024-06-04 8:52 ` Jeff King
2024-06-04 18:36 ` Junio C Hamano
2024-06-05 8:35 ` Jeff King
2024-06-05 16:30 ` Junio C Hamano
2024-06-04 8:59 ` Christian Couder
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=Zl7LEHFq4FcXMvGd@framework \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).