git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #09; Mon, 22)
Date: Wed, 24 Sep 2025 08:44:02 +0200	[thread overview]
Message-ID: <aNOTMtVC0ArCSTRS@szeder.dev> (raw)
In-Reply-To: <xmqqldm6qehe.fsf@gitster.g>

> * jt/odb-transaction (2025-09-16) 7 commits
>  - odb: add transaction interface
>  - object-file: update naming from bulk-checkin
>  - object-file: relocate ODB transaction code
>  - bulk-checkin: drop flush_odb_transaction()
>  - builtin/update-index: end ODB transaction when --verbose is specified
>  - bulk-checkin: remove ODB transaction nesting
>  - Merge branch 'jt/de-global-bulk-checkin' into jt/odb-transaction
> 
>  Continue the work to build on the bulk-checkin infrastructure to
>  create many objects at once in a transaction and abstract it into
>  the generic object layer.
> 
>  Will merge to 'next'.
>  source: <20250916182938.2193476-1-jltobler@gmail.com>

The merge of this topic into 'jch' modifies 'object-file.c' by
replacing a call to reprepare_packed_git() with odb_reprepare(), but
at that point the latter function doesn't exists yet, as it will only
be introduced in 'ps/packfile-store', which is merged later.

Interestingly, when I tried to recreate the same merge I got a
conflict only in 'odb.h', but not in 'object-file.c'.


> * ps/packfile-store (2025-09-15) 16 commits
>  - packfile: refactor `get_packed_git_mru()` to work on packfile store
>  - packfile: refactor `get_all_packs()` to work on packfile store
>  - packfile: refactor `get_packed_git()` to work on packfile store
>  - packfile: move `get_multi_pack_index()` into "midx.c"
>  - packfile: introduce function to load and add packfiles
>  - packfile: refactor `install_packed_git()` to work on packfile store
>  - packfile: split up responsibilities of `reprepare_packed_git()`
>  - packfile: refactor `prepare_packed_git()` to work on packfile store
>  - packfile: reorder functions to avoid function declaration
>  - odb: move kept cache into `struct packfile_store`
>  - odb: move MRU list of packfiles into `struct packfile_store`
>  - odb: move packfile map into `struct packfile_store`
>  - odb: move initialization bit into `struct packfile_store`
>  - odb: move list of packfiles into `struct packfile_store`
>  - packfile: introduce a new `struct packfile_store`
>  - Merge branch 'ps/object-store-midx-dedup-info' into ps/packfile-store
> 
>  Code clean-up around the in-core list of all the pack files and
>  object database(s).
> 
>  Expecting a reroll.
>  cf. <aMe_Zu1osrfDnSYL@pks.im>
>  source: <20250915-b4-pks-packfiles-store-v5-0-d6340350934f@pks.im>

  parent reply	other threads:[~2025-09-24  6:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 23:01 What's cooking in git.git (Sep 2025, #09; Mon, 22) Junio C Hamano
2025-09-23  3:19 ` Jeff King
2025-09-23 14:14   ` Junio C Hamano
2025-09-23  7:42 ` Patrick Steinhardt
2025-09-23 14:34   ` Junio C Hamano
2025-09-24  6:44 ` SZEDER Gábor [this message]
2025-09-24  7:00   ` Patrick Steinhardt
2025-09-24 19:01   ` 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=aNOTMtVC0ArCSTRS@szeder.dev \
    --to=szeder.dev@gmail.com \
    --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).