What's cooking (2025/09 #01)

todo
Junio C Hamano 2025-09-02 08:34:50 -07:00
parent aa78479fd9
commit 0bfa84918c
1 changed files with 27 additions and 147 deletions

View File

@ -1,10 +1,10 @@
To: git@vger.kernel.org
Subject: What's cooking in git.git (Aug 2025, #12; Fri, 29)
Subject: What's cooking in git.git (Sep 2025, #01; Tue, 2)
X-master-at: 6ad802182101d622e6a4132f48292ddfa79e2024
X-next-at: 3baa7cb742e267e07c93c00c15fa04107b8e9fab
X-next-at: 4c02a37b29ea955e35380eada24af394d7169ebf
Bcc: lwn@lwn.net, gitster@pobox.com

What's cooking in git.git (Aug 2025, #12; Fri, 29)
What's cooking in git.git (Sep 2025, #01; Tue, 2)
--------------------------------------------------

Here are the topics that have been cooking in my tree. Commits
@ -46,132 +46,7 @@ Release tarballs are available at:
https://www.kernel.org/pub/software/scm/git/

--------------------------------------------------
[Graduated to 'master']

* ad/t1517-short-help-tests-fix (2025-08-19) 1 commit
(merged to 'next' on 2025-08-21 at f686ad352a)
+ t/t1517: mark tests that fail with GIT_TEST_INSTALLED

Test fix.
source: <20250819074631.3303-1-adam@dinwoodie.org>


* bc/doc-compat-object-format-not-working (2025-08-25) 1 commit
(merged to 'next' on 2025-08-26 at 5224444f11)
+ docs: note that extensions.compatobjectformat is incomplete

The compatObjectFormat extension is used to hide an incomplete
feature that is not yet usable for any purpose other than
developing the feature further. Document it as such to discourage
its use by mere mortals.
source: <20250825221101.611876-1-sandals@crustytoothpaste.net>


* ds/doc-community-discord (2025-08-20) 1 commit
(merged to 'next' on 2025-08-21 at 7f9aa8da4e)
+ doc: add discord to ways of getting help

Discord has been added to the first contribution documentation as
another way to ask for help.
source: <pull.2033.v3.git.git.1755679018997.gitgitgadget@gmail.com>


* je/doc-rebase (2025-08-22) 5 commits
(merged to 'next' on 2025-08-26 at 0d9a1d75d5)
+ doc: git-rebase: update discussion of internals
+ doc: git-rebase: move --onto explanation down
+ doc: git rebase: clarify arguments syntax
+ doc: git rebase: dedup merge conflict discussion
+ doc: git-rebase: start with an example

Documentation for "git rebase" has been updated.
source: <pull.1949.v9.git.1755909782.gitgitgadget@gmail.com>


* jk/describe-blob (2025-08-18) 5 commits
(merged to 'next' on 2025-08-21 at 671998ff24)
+ describe: pass commit to describe_commit()
+ describe: handle blob traversal with no commits
+ describe: catch unborn branch in describe_blob()
+ describe: error if blob not found
+ describe: pass oid struct by const pointer

"git describe <blob>" misbehaves and/or crashes in some corner
cases, which has been taught to exit with failure gracefully.
source: <20250818205812.GA1018043@coredump.intra.peff.net>


* jk/fetch-check-graph-objects-fix (2025-08-23) 1 commit
(merged to 'next' on 2025-08-26 at 51a561116f)
+ fetch-pack: re-scan when double-checking graph objects

Under a race against another process that is repacking the
repository, especially a partially cloned one, "git fetch" may
mistakenly think some objects we do have are missing, which has
been corrected.
source: <20250824050040.GA228050@coredump.intra.peff.net>


* jk/no-clobber-dangling-symref-with-fetch (2025-08-19) 4 commits
(merged to 'next' on 2025-08-21 at 29b96663c0)
+ refs: do not clobber dangling symrefs
+ t5510: prefer "git -C" to subshell for followRemoteHEAD tests
+ t5510: stop changing top-level working directory
+ t5510: make confusing config cleanup more explicit

"git fetch" can clobber a symref that is dangling when the
remote-tracking HEAD is set to auto update, which has been
corrected.
source: <20250819192004.GA1058857@coredump.intra.peff.net>


* js/doc-gitk-history (2025-08-19) 1 commit
(merged to 'next' on 2025-08-21 at e7e1a08f82)
+ doc/gitk: update reference to the external project

Manual page for "gitk" is updated with the current maintainer's
name.
source: <249056e7-1332-4e6f-8d07-16c80fd4913e@kdbg.org>


* js/progress-delay-fix (2025-08-25) 1 commit
(merged to 'next' on 2025-08-26 at 4e832eb295)
+ progress: pay attention to (customized) delay time

The start_delayed_progress() function in the progress eye-candy API
did not clear its internal state, making an initial delay value
larger than 1 second ineffective, which has been corrected.
source: <7b848623-ce64-4679-9b5e-9d91d947b269@kdbg.org>


* ps/reftable-libgit2-cleanup (2025-08-12) 8 commits
(merged to 'next' on 2025-08-21 at ff82e3fa11)
+ refs/reftable: always reload stacks when creating lock
+ reftable: don't second-guess errors from flock interface
+ reftable/stack: handle outdated stacks when compacting
+ reftable/stack: allow passing flags to `reftable_stack_add()`
+ reftable/stack: fix compiler warning due to missing braces
+ reftable/stack: reorder code to avoid forward declarations
+ reftable/writer: drop Git-specific `QSORT()` macro
+ reftable/writer: fix type used for number of records

Code clean-ups.
source: <20250812-pks-reftable-fixes-for-libgit2-v3-0-cf3b2267867e@pks.im>


* sg/line-log-merge-optim (2025-08-24) 4 commits
(merged to 'next' on 2025-08-26 at e110ef974a)
+ line-log: simplify condition checking for merge commits
+ line-log: initialize diff queue in process_ranges_ordinary_commit()
+ line-log: get rid of the parents array in process_ranges_merge_commit()
+ line-log: avoid unnecessary tree diffs when processing merge commits

"git log -L..." compared trees of multiple parents with the tree of the
merge result in an unnecessarily inefficient way.
source: <20250824190644.2573279-1-szeder.dev@gmail.com>

--------------------------------------------------
[New Topics]
[Cooking]

* ag/doc-sendmail-gmail-example-update (2025-08-26) 1 commit
- docs: update sendmail docs to use more secure SMTP server for Gmail
@ -183,12 +58,13 @@ Release tarballs are available at:


* da/cargo-serialize (2025-08-26) 1 commit
- Makefile: build libgit-rs and libgit-sys serially
(merged to 'next' on 2025-08-29 at 5a193b1525)
+ Makefile: build libgit-rs and libgit-sys serially

Makefile tried to run multiple "cargo build" which would not work
very well; serialize their execution to work it around.

Will merge to 'next'.
Will merge to 'master'.
source: <20250826233525.2635432-1-davvid@gmail.com>


@ -250,14 +126,15 @@ Release tarballs are available at:


* ds/ls-files-lazy-unsparse (2025-08-15) 1 commit
- ls-files: conditionally leave index sparse
(merged to 'next' on 2025-08-29 at a48fee2dde)
+ ls-files: conditionally leave index sparse

"git ls-files <pathspec>..." should not necessarily have to expand
the index fully if a sparsified directory is excluded by the
pathspec; the code is taught to expand the index on demand to avoid
this.

Will merge to 'next'.
Will merge to 'master'.
source: <pull.1955.git.1755274373717.gitgitgadget@gmail.com>


@ -281,8 +158,6 @@ Release tarballs are available at:
Will merge to 'next'?
source: <pull.2040.v3.git.git.1756472406487.gitgitgadget@gmail.com>

--------------------------------------------------
[Cooking]

* ds/doc-ggg-pr-fork-clarify (2025-08-23) 1 commit
(merged to 'next' on 2025-08-25 at 71aea64ee4)
@ -412,25 +287,28 @@ Release tarballs are available at:
source: <20250816213642.3517822-1-adrian.ratiu@collabora.com>


* je/doc-add (2025-08-19) 2 commits
* je/doc-add (2025-08-29) 3 commits
- doc: rephrase the purpose of the staging area
(merged to 'next' on 2025-08-25 at 0c84501ed2)
+ doc: git-add: simplify discussion of ignored files
+ doc: git-add: clarify intro & add an example

Documentation for "git add" has been updated.

Will merge to 'master'.
Will merge to 'next' and then to 'master'.
source: <pull.1952.v3.git.1755636370.gitgitgadget@gmail.com>
source: <pull.1952.v4.git.1756468502.gitgitgadget@gmail.com>


* ds/path-walk-repack-fix (2025-08-25) 2 commits
- path-walk: create initializer for path lists
- path-walk: fix setup of pending objects
(merged to 'next' on 2025-08-29 at 13028ffb8e)
+ path-walk: create initializer for path lists
+ path-walk: fix setup of pending objects

"git repack --path-walk" lost objects in some corner cases, which
has been corrected.

Will merge to 'next'.
Will merge to 'master'.
cf. <CABPp-BHFxxGrqKc0m==TjQNjDGdO=H5Rf6EFsf2nfE1=TuraOQ@mail.gmail.com>
source: <pull.1956.v2.git.1756126197.gitgitgadget@gmail.com>

@ -510,14 +388,15 @@ Release tarballs are available at:


* am/xdiff-hash-tweak (2025-07-28) 2 commits
- xdiff: optimize xdl_hash_record_verbatim
- xdiff: refactor xdl_hash_record()
(merged to 'next' on 2025-08-29 at 43590f0b38)
+ xdiff: optimize xdl_hash_record_verbatim
+ xdiff: refactor xdl_hash_record()

Inspired by Ezekiel's recent effort to showcase Rust interface, the
hash function implementation used to hash lines have been updated
to the one used for ELF symbol lookup by Glibc.

Will merge to 'next'.
Will merge to 'master'.
cf. <xmqqecsvqal6.fsf@gitster.g>
source: <20250728190520.10962-1-amonakov@ispras.ru>

@ -570,14 +449,15 @@ Release tarballs are available at:


* tc/last-modified (2025-08-05) 3 commits
- last-modified: use Bloom filters when available
- t/perf: add last-modified perf script
- last-modified: new subcommand to show when files were last modified
(merged to 'next' on 2025-08-29 at 3f3e111189)
+ last-modified: use Bloom filters when available
+ t/perf: add last-modified perf script
+ last-modified: new subcommand to show when files were last modified

A new command "git last-modified" is proposed to show the closest
ancestor commit that touched each path.

Will merge to 'next'.
Will merge to 'master'.
source: <20250730175510.987383-1-toon@iotcl.com>