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 (Feb 2026, #05)
Date: Mon, 16 Feb 2026 07:56:40 +0100 [thread overview]
Message-ID: <aZK_qHzKslgb_P_O@pks.im> (raw)
In-Reply-To: <xmqq4inkhymy.fsf@gitster.g>
On Fri, Feb 13, 2026 at 06:01:09PM -0800, Junio C Hamano wrote:
> * ps/pack-concat-wo-backfill (2026-02-11) 1 commit
> - builtin/pack-objects: don't fetch objects when merging packs
>
> "git pack-objects --stdin-packs" with "--exclude-promisor-objects"
> fetched objects that are promised, which was not wanted. This has
> been fixed.
>
> Will merge to 'next'?
> source: <20260211-pks-pack-objects-stdin-skip-backfill-fetch-v1-1-870cad56d8ae@pks.im>
Yeah, all the reviews have been favorable here, so I think this is ready
for next.
> * jc/doc-cg-needswork (2026-02-12) 1 commit
> - CodingGuidelines: document NEEDSWORK comments
>
> A CodingGuidelines update.
>
> Will merge to 'next'?
> source: <xmqqldgxmzbj.fsf@gitster.g>
There's still the one grammar issue pointed out in [1], but once that's
fixed I think it can be merged.
> * ps/history-ergonomics-updates (2026-02-13) 5 commits
> - Documentation/git-history: document default for "--update-refs="
> - builtin/history: rename "--ref-action=" to "--update-refs="
> - builtin/history: replace "--ref-action=print" with "--dry-run"
> - builtin/history: check for merges before asking for user input
> - builtin/history: perform revwalk checks before asking for user input
>
> UI improvements for "git history reword".
>
> Will merge to 'next'?
> source: <20260213-b4-pks-history-dry-run-v2-0-756ac376e9e5@pks.im>
I've sent out v3 to fix up a small typo here.
> * ps/meson-gitk-git-gui (2026-02-04) 1 commit
> - meson: wire up gitk and git-gui
>
> Plumb gitk/git-gui build and install procedure in meson based
> builds.
>
> Expecting a pull request for gitk.
> source: <20260204-b4-pks-meson-tcl-tk-v2-1-5bc3ccf3a8ce@pks.im>
That PR for gitk has been merged now. The build for git-gui still has
some issues (e.g. no askyesno helper), and fixes for this are in review
upstream [2]. I think it's fine to merge this regardless as it won't
cause builds to fail, but I'm also happy to wait for the git-gui bits to
settle first.
> * jc/checkout-switch-restore (2026-01-29) 2 commits
> - checkout: tell "parse_remote_branch" which command is calling it
> - checkout: pass program-readable token to unified "main"
>
> "git switch <name>", in an attempt to create a local branch <name>
> after a remote tracking branch of the same name gave an advise
> message to disambiguate using "git checkout", which has been
> updated to use "git switch".
>
> Will merge to 'next'?
> source: <20260129190616.645471-1-gitster@pobox.com>
I think this is good to go.
> * ps/for-each-ref-in-fixes (2026-02-05) 4 commits
> - bisect: simplify string_list memory handling
> - bisect: fix misuse of `refs_for_each_ref_in()`
> - pack-bitmap: fix bug with exact ref match in "pack.preferBitmapTips"
> - pack-bitmap: deduplicate logic to iterate over preferred bitmap tips
>
> A handful of places used refs_for_each_ref_in() API incorrectly,
> which has been corrected.
>
> Will merge to 'next'?
> cf. <aYmleK3kGqzLXyJe@pks.im>
> source: <20260206-b4-pks-fix-for-each-ref-in-misuse-v3-0-1e050c3d6a50@pks.im>
This has been cooking for a while, and the latest version did address
all feedback. So maybe it's time to merge this down now.
> * ps/object-info-bits-cleanup (2026-02-11) 5 commits
> - odb: convert `odb_has_object()` flags into an enum
> - odb: convert object info flags into an enum
> - odb: drop gaps in object info flag values
> - builtin/fsck: fix flags passed to `odb_has_object()`
> - builtin/backfill: fix flags passed to `odb_has_object()`
>
> A couple of bugs in use of flag bits around odb API has been
> corrected, and the flag bits reordered.
>
> Will merge to 'next'?
> source: <20260212-b4-pks-read-object-info-flags-v2-0-3bfa9bb149ef@pks.im>
Fine with me.
> * ps/odb-for-each-object (2026-01-26) 16 commits
> - odb: drop unused `for_each_{loose,packed}_object()` functions
> - reachable: convert to use `odb_for_each_object()`
> - builtin/pack-objects: use `packfile_store_for_each_object()`
> - odb: introduce mtime fields for object info requests
> - treewide: drop uses of `for_each_{loose,packed}_object()`
> - treewide: enumerate promisor objects via `odb_for_each_object()`
> - builtin/fsck: refactor to use `odb_for_each_object()`
> - odb: introduce `odb_for_each_object()`
> - packfile: introduce function to iterate through objects
> - packfile: extract function to iterate through objects of a store
> - object-file: introduce function to iterate through objects
> - object-file: extract function to read object info from path
> - odb: fix flags parameter to be unsigned
> - odb: rename `FOR_EACH_OBJECT_*` flags
> - Merge branch 'ps/packfile-store-in-odb-source' into ps/odb-for-each-object
> - Merge branch 'ps/read-object-info-improvements' into ps/odb-for-each-object
>
> Revamp object enumeration API around odb.
>
> Will merge to 'next'?
> cf. <aXk2FjTUMMThs5Kp@nand.local>
> source: <20260126-pks-odb-for-each-object-v4-0-5a64a038c791@pks.im>
Same here, this has been cooking for a long time by now, and the
discussion around mtime has stalled after I clarified intentions and
future plans to evolve it further. So I'd love to see this merged.
Thanks!
Patrick
[1]: <aZBMQGQPiE3cJBUq@ugly.lan>
[2]: https://github.com/j6t/git-gui/pull/31
prev parent reply other threads:[~2026-02-16 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 2:01 What's cooking in git.git (Feb 2026, #05) Junio C Hamano
2026-02-14 21:17 ` ds/revision-maximal-only (was Re: What's cooking in git.git (Feb 2026, #05)) Derrick Stolee
2026-02-17 16:33 ` Junio C Hamano
2026-02-16 6:56 ` Patrick Steinhardt [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=aZK_qHzKslgb_P_O@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