Git development
 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 (Jul 2026, #01)
Date: Thu, 2 Jul 2026 12:38:25 +0200	[thread overview]
Message-ID: <akY_oce1EcsgsN9b@pks.im> (raw)
In-Reply-To: <xmqqv7ayl1nj.fsf@gitster.g>

On Wed, Jul 01, 2026 at 04:40:16PM -0700, Junio C Hamano wrote:
> * ps/odb-drop-whence (2026-06-24) 7 commits
>  - odb: document object info fields
>  - odb: drop `whence` field from object info
>  - treewide: convert users of `whence` to the new source field
>  - odb: add `source` field to struct object_info_source
>  - odb: make backend-specific fields optional
>  - packfile: thread odb_source_packed through packed_object_info()
>  - Merge branch 'ps/odb-source-packed' into ps/odb-drop-whence
>  (this branch uses ps/odb-source-packed.)
> 
>  The whence field in struct object_info has been removed,
>  refactoring backend-specific object information retrieval into an
>  opt-in struct object_info_source structure.
> 
>  Will merge to 'next'?
>  cf. <akOod6X1a2axIXKZ@pks.im>
>  cf. <xmqqv7b0rmt6.fsf@gitster.g>
>  source: <20260624-b4-pks-odb-drop-whence-v1-0-8d1877b790ac@pks.im>

I'll send a small reroll to rename `sourcep` to `source_infop` based on
Justin's feedback.

> * ps/odb-generalize-prepare (2026-06-22) 3 commits
>  - odb: introduce `odb_prepare()`
>  - odb/source: generalize `reprepare()` callback
>  - Merge branch 'ps/odb-source-packed' into ps/odb-generalize-prepare
>  (this branch uses ps/odb-source-packed.)
> 
>  The `reprepare()` callback for object database sources has been
>  generalized into a `prepare()` callback with an optional flush cache
>  flag, and a new `odb_prepare()` wrapper has been introduced to
>  allow pre-opening object database sources.
> 
>  Will merge to 'next'?
>  cf. <87ik704f1j.fsf@emacs.iotcl.com>
>  source: <20260622-b4-pks-odb-generalize-prepare-v1-0-d2a5c5d13144@pks.im>

This one should be ready.

> * ps/refs-writing-subcommands (2026-06-30) 5 commits
>  - builtin/refs: add "rename" subcommand
>  - builtin/refs: add "create" subcommand
>  - builtin/refs: add "update" subcommand
>  - builtin/refs: add "delete" subcommand
>  - builtin/refs: drop `the_repository`
> 
>  The "git refs" toolbox has been extended with new "create", "delete",
>  "update", and "rename" subcommands to create, delete, update, and
>  rename references, respectively.
> 
>  Will merge to 'next'?
>  cf. <xmqqcxx7susi.fsf@gitster.g>
>  source: <20260630-pks-refs-writing-subcommands-v3-0-deb04de1ecef@pks.im>

Likewise.

Thanks!

Patrick

  reply	other threads:[~2026-07-02 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 23:40 What's cooking in git.git (Jul 2026, #01) Junio C Hamano
2026-07-02 10:38 ` Patrick Steinhardt [this message]
2026-07-03 20:39   ` 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=akY_oce1EcsgsN9b@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