git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: karthik nayak <karthik.188@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #09; Mon, 25)
Date: Wed, 27 Nov 2024 12:19:42 +0000	[thread overview]
Message-ID: <CAOLa=ZTHVdJxq+vcAGMRMS3A53m_a38npEJgiF7xLd-3J6MiLg@mail.gmail.com> (raw)
In-Reply-To: <xmqqttbv4ty8.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]

Junio C Hamano <gitster@pobox.com> writes:

[snip]

> [Cooking]
>
> * kn/midx-wo-the-repository (2024-11-25) 11 commits
>  - midx: inline the `MIDX_MIN_SIZE` definition
>  - midx: pass down `hash_algo` to `get_split_midx_filename_ext`
>  - midx: pass down `hash_algo` to `get_midx_filename[_ext]`
>  - midx: pass `repository` to `load_multi_pack_index`
>  - midx: cleanup internal usage of `the_repository` and `the_hash_algo`
>  - midx-write: pass down repository to `write_midx_file[_only]`
>  - write-midx: add repository field to `write_midx_context`
>  - midx-write: use `revs->repo` inside `read_refs_snapshot`
>  - midx-write: pass down repository to static functions
>  - builtin: pass repository to sub commands
>  - Merge branch 'kn/the-repository' into kn/midx-wo-the-repository
>  (this branch uses kn/the-repository.)
>
>  Yet another "pass the repository through the callchain" topic.
>
>  Expecting a reroll.
>  source: <20241119-374-refactor-midx-c-and-midx-write-c-to-not-depend-on-global-state-v2-0-e2f607174efc@gmail.com>
>

I'm waiting for
https://lore.kernel.org/git/xmqq34jdyey3.fsf@gitster.g/T/#t settle down,
and I'll then rebase and send this.

[snip]

> * kn/the-repository (2024-11-25) 10 commits
>  - packfile.c: remove unnecessary prepare_packed_git() call
>  - midx: add repository to `multi_pack_index` struct
>  - config: make `packed_git_(limit|window_size)` non-global variables
>  - config: make `delta_base_cache_limit` a non-global variable
>  - packfile: pass down repository to `for_each_packed_object`
>  - packfile: pass down repository to `has_object[_kept]_pack`
>  - packfile: pass down repository to `odb_pack_name`
>  - packfile: pass `repository` to static function in the file
>  - packfile: use `repository` from `packed_git` directly
>  - packfile: add repository to struct `packed_git`
>  (this branch is used by kn/midx-wo-the-repository.)
>
>  Various implicit uses of 'the_repoository' in the packfile code
>  have been eliminated.
>
>  Will merge to 'next'?
>  source: <cover.1732269840.git.karthik.188@gmail.com>

There were two commit message changes suggested by Kristoffer, I'm not
sure they require a re-roll. But otherwise, I think it should be ready
to be merged to next.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 690 bytes --]

      parent reply	other threads:[~2024-11-27 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25  8:07 What's cooking in git.git (Nov 2024, #09; Mon, 25) Junio C Hamano
2024-11-27  8:30 ` Patrick Steinhardt
2024-11-28  1:57   ` Junio C Hamano
2024-11-27 12:19 ` karthik nayak [this message]

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='CAOLa=ZTHVdJxq+vcAGMRMS3A53m_a38npEJgiF7xLd-3J6MiLg@mail.gmail.com' \
    --to=karthik.188@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).