git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 (Nov 2025, #10; Sun, 30)
Date: Mon, 1 Dec 2025 10:54:25 +0100	[thread overview]
Message-ID: <aS1l0YuU9xOE7eog@pks.im> (raw)
In-Reply-To: <xmqq5xaqbxmk.fsf@gitster.g>

On Sun, Nov 30, 2025 at 09:05:07PM -0800, Junio C Hamano wrote:
> * ps/object-read-stream (2025-11-23) 20 commits
>  - streaming: drop redundant type and size pointers
>  - streaming: move into object database subsystem
>  - streaming: refactor interface to be object-database-centric
>  - streaming: move logic to read packed objects streams into backend
>  - streaming: move logic to read loose objects streams into backend
>  - streaming: make the `odb_read_stream` definition public
>  - streaming: get rid of `the_repository`
>  - streaming: rely on object sources to create object stream
>  - packfile: introduce function to read object info from a store
>  - streaming: move zlib stream into backends
>  - streaming: create structure for filtered object streams
>  - streaming: create structure for packed object streams
>  - streaming: create structure for loose object streams
>  - streaming: create structure for in-core object streams
>  - streaming: allocate stream inside the backend-specific logic
>  - streaming: explicitly pass packfile info when streaming a packed object
>  - streaming: propagate final object type via the stream
>  - streaming: drop the `open()` callback function
>  - streaming: rename `git_istream` into `odb_read_stream`
>  - Merge branch 'ps/object-source-loose' into ps/object-read-stream
> 
>  The "git_istream" abstraction has been revamped to make it easier
>  to interface with pluggable object database design.
> 
>  Will merge to 'next'?
>  source: <20251123-b4-pks-odb-read-stream-v3-0-1a129182822b@pks.im>

I think this topic should be ready for next. The latest version didn't
receive any feedback, but all it did is to improve some commit messages
and rename a function based on previous reviews.

> * ps/history (2025-10-27) 12 commits
>  - builtin/history: implement "split" subcommand
>  - cache-tree: allow writing in-memory index as tree
>  - add-patch: add support for in-memory index patching
>  - add-patch: remove dependency on "add-interactive" subsystem
>  - add-patch: split out `struct interactive_options`
>  - add-patch: split out header from "add-interactive.h"
>  - builtin/history: implement "reword" subcommand
>  - builtin: add new "history" command
>  - replay: stop using `the_repository`
>  - replay: extract logic to pick commits
>  - wt-status: provide function to expose status for trees
>  - Merge branch 'sa/replay-atomic-ref-updates' into ps/history
>  (this branch is used by pw/replay-drop-empty.)
> 
>  "git history" history rewriting UI.
> 
>  Expecting a reroll.
>  cf. <aRxDYkeAi8T-HH8M@pks.im>
>  source: <20251027-b4-pks-history-builtin-v6-0-407dd3f57ad3@pks.im>

I'll address feedback on this topic later this week.

Thanks!

Patrick

  reply	other threads:[~2025-12-01  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  5:05 What's cooking in git.git (Nov 2025, #10; Sun, 30) Junio C Hamano
2025-12-01  9:54 ` Patrick Steinhardt [this message]
2025-12-01 10:53 ` Karthik Nayak
2025-12-07  0:43   ` Junio C Hamano
2025-12-01 11:43 ` Jeff King
2025-12-08  8:44   ` Adrian Ratiu

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=aS1l0YuU9xOE7eog@pks.im \
    --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).