What's cooking (2024/12 #08)
Junio C Hamano committed
Dec 23, 2024 at 10:52 UTC
708d69bd9454e83486c3889e282559ba03f80ed0
1 file changed
+231
-268
whats-cooking.txt
+231
-268
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
-Subject: What's cooking in git.git (Dec 2024, #07; Thu, 19)
3
-X-master-at: ff795a5c5ed2e2d07c688c217a615d89e3f5733b
4
-X-next-at: 3cddc25e2affa62f1ee18d86e121316d5861298b
2
+Subject: What's cooking in git.git (Dec 2024, #08; Mon, 23)
3
+X-master-at: 996f0c583b36aa5d6c6308285aea1421eb7efae7
4
+X-next-at: 73897bcc729bd26ea18552b27e1ed5ffad93a951
5
Bcc: lwn@lwn.net, gitster@pobox.com
6
7
-What's cooking in git.git (Dec 2024, #07; Thu, 19)
7
+What's cooking in git.git (Dec 2024, #08; Mon, 23)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -17,10 +17,11 @@ topic without enough support may be discarded after a long period of
17
no activity (of course they can be resubmit when new interests
18
arise).
19
20
-An early preview release Git 2.48-rc0 has been tagged. The rate of
21
-arrival of new topics unfortunately exceeds the rate of reviews and
22
-iterations, which means that many topics are left out of 'next',
23
-waiting to be reviewed.
20
+Let's wait for git-gui, gitk, and possibly po/ and delay the tagging
21
+of the -rc1. Many people are already offline for the end-of-year
22
+holidays and it is a slow week, and 'master' front has too many new
23
+things graduated from 'next' a bit too early for me to feel
24
+comfortable.
25
26
Copies of the source code to Git live in many repositories, and the
27
following is a list of the ones I push into or their mirrors. Some
@@ -53,93 +54,22 @@ Release tarballs are available at:
54
--------------------------------------------------
55
[Graduated to 'master']
56
56
-* bf/fetch-set-head-config (2024-12-06) 5 commits
57
- (merged to 'next' on 2024-12-11 at 900cadd7b7)
58
- + remote set-head: set followRemoteHEAD to "warn" if "always"
59
- + fetch set_head: add warn-if-not-$branch option
60
- + fetch set_head: move warn advice into advise_if_enabled
61
- (merged to 'next' on 2024-12-04 at 69bfc59fb5)
62
- + fetch: add configuration for set_head behaviour
63
- + Merge branch 'bf/set-head-symref' into bf/fetch-set-head-config
64
- (this branch uses bf/set-head-symref.)
65
-
66
- "git fetch" honors "remote.<remote>.followRemoteHEAD" settings to
67
- tweak the remote-tracking HEAD in "refs/remotes/<remote>/HEAD".
68
-
69
- Will merge to 'master' after bf/set-head-symref and its fix-up.
70
- source: <20241128230806.2058962-1-bence@ferdinandy.com>
71
- source: <20241204104003.514905-1-bence@ferdinandy.com>
72
- source: <20241128111946.366584-1-bence@ferdinandy.com>
73
-
74
-
75
-* bf/set-head-symref (2024-11-25) 10 commits
76
- (merged to 'next' on 2024-12-02 at b142ff3d8e)
77
- + fetch set_head: handle mirrored bare repositories
78
- + fetch: set remote/HEAD if it does not exist
79
- + refs: add create_only option to refs_update_symref_extended
80
- + refs: add TRANSACTION_CREATE_EXISTS error
81
- + remote set-head: better output for --auto
82
- + remote set-head: refactor for readability
83
- + refs: atomically record overwritten ref in update_symref
84
- + refs: standardize output of refs_read_symbolic_ref
85
- + t/t5505-remote: test failure of set-head
86
- + t/t5505-remote: set default branch to main
87
- (this branch is used by bf/fetch-set-head-config and jc/set-head-symref-fix.)
88
-
89
- When "git fetch $remote" notices that refs/remotes/$remote/HEAD is
90
- missing and discovers what branch the other side points with its
91
- HEAD, refs/remotes/$remote/HEAD is updated to point to it.
92
-
93
- Will merge to 'master' together with jc/set-head-symref-fix.
94
- source: <20241122123138.66960-1-bence@ferdinandy.com>
95
-
96
-
97
-* jc/set-head-symref-fix (2024-12-07) 2 commits
98
- (merged to 'next' on 2024-12-13 at 478444359e)
99
- + fetch: do not ask for HEAD unnecessarily
100
- + Merge branch 'bf/set-head-symref' into js/set-head-symref-fix
101
- (this branch uses bf/set-head-symref.)
102
-
103
- "git fetch" from a configured remote learned to update a missing
104
- remote-tracking HEAD but it asked the remote about their HEAD even
105
- when it did not need to, which has been corrected. Incidentally,
106
- this also corrects "git fetch --tags $URL" which was broken by the
107
- new feature in an unspecified way.
108
-
109
- source: <xmqqcyi5xmhr.fsf@gitster.g>
110
-
111
-
112
-* js/log-remerge-keep-ancestry (2024-12-13) 1 commit
113
- (merged to 'next' on 2024-12-13 at 90156d79ed)
114
- + log: --remerge-diff needs to keep around commit parents
115
- (this branch is used by js/range-diff-diff-merges.)
116
-
117
- "git log -p --remerge-diff --reverse" was completely broken.
118
-
119
- source: <pull.1825.v3.git.1733999352289.gitgitgadget@gmail.com>
120
-
121
-
122
-* mh/doc-windows-home-env (2024-12-10) 1 commit
123
- (merged to 'next' on 2024-12-13 at 9f49e6f9dd)
124
- + Document HOME environment variable
125
-
126
- Doc update.
127
-
128
- source: <pull.1834.git.1733771894867.gitgitgadget@gmail.com>
129
-
130
-
131
-* tc/bundle-with-tag-remove-workaround (2024-12-12) 1 commit
132
- (merged to 'next' on 2024-12-13 at 7f4ebe0be3)
133
- + bundle: remove unneeded code
134
-
135
- "git bundle create" with an annotated tag on the positive end of
136
- the revision range had a workaround code for older limitation in
137
- the revision walker, which has become unnecessary.
138
-
139
- source: <20241211-fix-bundle-create-race-v3-1-0587f6f9db1b@iotcl.com>
57
+* as/show-index-uninitialized-hash (2024-11-11) 2 commits
58
+ (merged to 'next' on 2024-12-16 at b54e9a56f0)
59
+ + t5300: add test for 'show-index --object-format'
60
+ + show-index: fix uninitialized hash function
61
+
62
+ Regression fix for 'show-index' when run outside of a repository.
63
+ source: <20241109092739.14276-1-abhijeet.nkt@gmail.com>
64
+
65
+
66
+* jk/prio-queue-sign-compare-fix (2024-12-20) 1 commit
67
+ (merged to 'next' on 2024-12-21 at 11a5c3d11f)
68
+ + prio-queue: use size_t rather than int for size
69
+
70
+ Type clean-up.
71
+ source: <20241220084949.GA132704@coredump.intra.peff.net>
72
141
---------------------------------------------------
142
-[New Topics]
73
74
* js/github-windows-setup-fix (2024-12-17) 1 commit
75
(merged to 'next' on 2024-12-17 at 6d59340ec5)
@@ -147,8 +77,6 @@ Release tarballs are available at:
77
78
Revert recent changes to the way windows environment is set up for
79
GitHub CI.
150
-
151
- Will merge to 'master'.
80
source: <pull.1841.git.1734447458896.gitgitgadget@gmail.com>
81
82
@@ -158,8 +86,6 @@ Release tarballs are available at:
86
87
Update the way rename() emulation on Windows handle directories to
88
correct an earlier attempt to do the same.
161
-
162
- Will merge to 'master'.
89
source: <pull.1839.git.1734439924842.gitgitgadget@gmail.com>
90
91
@@ -172,43 +98,165 @@ Release tarballs are available at:
98
+ cmake: better support for out-of-tree builds follow-up
99
100
Build fixes for Windows.
175
-
176
- Will merge to 'master'.
101
source: <pull.1840.git.1734456721.gitgitgadget@gmail.com>
102
103
104
+* js/range-diff-diff-merges (2024-12-16) 3 commits
105
+ (merged to 'next' on 2024-12-18 at 47394ea998)
106
+ + range-diff: introduce the convenience option `--remerge-diff`
107
+ + range-diff: optionally include merge commits' diffs in the analysis
108
+ + Merge branch 'js/log-remerge-keep-ancestry' into js/range-diff-diff-merges
109
+
110
+ "git range-diff" learned to optionally show and compare merge
111
+ commits in the ranges being compared, with the --diff-merges
112
+ option.
113
+ source: <pull.1734.v3.git.1734358282.gitgitgadget@gmail.com>
114
+
115
+
116
* kl/doc-build-fix (2024-12-17) 1 commit
181
- - doc: remove extra quotes in generated docs
117
+ (merged to 'next' on 2024-12-21 at d6f8295805)
118
+ + doc: remove extra quotes in generated docs
119
120
Build fix.
184
-
185
- Will merge to 'next'?
186
- More fixes to come.
187
- cf. <Z2LL9F8WANokZJ7R@pks.im>
121
source: <pull.1847.v2.git.git.1734483422181.gitgitgadget@gmail.com>
122
123
191
-* ps/the-repository (2024-12-18) 15 commits
192
- - match-trees: stop using `the_repository`
193
- - graph: stop using `the_repository`
194
- - add-interactive: stop using `the_repository`
195
- - tmp-objdir: stop using `the_repository`
196
- - resolve-undo: stop using `the_repository`
197
- - credential: stop using `the_repository`
198
- - mailinfo: stop using `the_repository`
199
- - diagnose: stop using `the_repository`
200
- - server-info: stop using `the_repository`
201
- - send-pack: stop using `the_repository`
202
- - serve: stop using `the_repository`
203
- - trace: stop using `the_repository`
204
- - pager: stop using `the_repository`
205
- - progress: stop using `the_repository`
206
- - Merge branch 'ps/build-sign-compare' into ps/the-repository
207
- (this branch uses ps/build-sign-compare.)
124
+* kn/reflog-migration (2024-12-20) 10 commits
125
+ (merged to 'next' on 2024-12-22 at b75456bef5)
126
+ + refs: mark invalid refname message for translation
127
+ (merged to 'next' on 2024-12-18 at 5634446b20)
128
+ + refs: add support for migrating reflogs
129
+ + refs: allow multiple reflog entries for the same refname
130
+ + refs: introduce the `ref_transaction_update_reflog` function
131
+ + refs: add `committer_info` to `ref_transaction_add_update()`
132
+ + refs: extract out refname verification in transactions
133
+ + refs/files: add count field to ref_lock
134
+ + refs: add `index` field to `struct ref_udpate`
135
+ + refs: include committer info in `ref_update` struct
136
+ + Merge branch 'kn/reftable-writer-log-write-verify' into kn/reflog-migration
137
+ (this branch uses kn/reftable-writer-log-write-verify.)
138
209
- More code paths have a repository passed through the callchain,
210
- instead of assuming the primary the_repository object.
211
- source: <20241217-pks-use-the-repository-conversion-v1-0-0dba48bcc239@pks.im>
139
+ "git refs migrate" learned to also migrate the reflog data across
140
+ backends.
141
+ source: <20241216-320-git-refs-migrate-reflogs-v4-0-d7cd3f197453@gmail.com>
142
+ source: <20241220125837.2774153-1-karthik.188@gmail.com>
143
+
144
+
145
+* kn/reftable-writer-log-write-verify (2024-12-07) 1 commit
146
+ (merged to 'next' on 2024-12-15 at 7e6b58d98e)
147
+ + reftable/writer: ensure valid range for log's update_index
148
+ (this branch is used by kn/reflog-migration.)
149
+
150
+ Reftable backend adds check for upper limit of log's update_index.
151
+ source: <20241206-424-reftable-writer-add-check-for-limits-v2-1-82ca350b10be@gmail.com>
152
+
153
+
154
+* ma/asciidoctor-build-fixes (2024-12-20) 4 commits
155
+ (merged to 'next' on 2024-12-22 at 7a2aad750e)
156
+ + asciidoctor-extensions.rb.in: inject GIT_DATE
157
+ + asciidoctor-extensions.rb.in: add missing word
158
+ + asciidoctor-extensions.rb.in: delete existing <refmiscinfo/>
159
+ + Merge branch 'ps/build-hotfix' into ma/asciidoctor-build-fixes
160
+ (this branch uses ps/build-hotfix.)
161
+
162
+ A topic to optionally build with meson, which has graduated to
163
+ 'master' recently, broke Documentation pipeline with asciidoctor
164
+ for the normal Makefile build as well as meson-based one, which
165
+ have been corrected.
166
+ cf. <Z2abxaGVzA5Kce-s@pks.im>
167
+ source: <cover.1734734612.git.martin.agren@gmail.com>
168
+
169
+
170
+* ps/build-hotfix (2024-12-20) 6 commits
171
+ (merged to 'next' on 2024-12-22 at 0d4dfd121e)
172
+ + meson: add options to override build information
173
+ + GIT-VERSION-GEN: fix overriding GIT_BUILT_FROM_COMMIT and GIT_DATE
174
+ + GIT-VERSION-GEN: fix overriding GIT_VERSION
175
+ + Makefile: introduce template for GIT-VERSION-GEN
176
+ + Makefile: drop unneeded indirection for GIT-VERSION-GEN outputs
177
+ + Makefile: stop including "GIT-VERSION-FILE" in docs
178
+ (this branch is used by ma/asciidoctor-build-fixes.)
179
+
180
+ A topic to optionally build with meson, which has graduated to
181
+ 'master' recently, has regressed the normal Makefile build, which
182
+ is being corrected.
183
+ source: <20241220-b4-pks-git-version-via-environment-v3-0-1fd79b52a5fb@pks.im>
184
+
185
+
186
+* ps/build-meson-gitweb (2024-12-20) 1 commit
187
+ (merged to 'next' on 2024-12-21 at f775554ea5)
188
+ + meson: skip gitweb build when Perl is disabled
189
+
190
+ meson-based build still tried to build and install gitweb even when
191
+ Perl is disabled, which has been corrected.
192
+ source: <20241220-b4-pks-meson-fix-gitweb-wo-perl-v2-1-18ab23dd6446@pks.im>
193
+
194
+
195
+* ps/build-sign-compare (2024-12-06) 16 commits
196
+ (merged to 'next' on 2024-12-16 at 1ddb1485df)
197
+ + t/helper: don't depend on implicit wraparound
198
+ + scalar: address -Wsign-compare warnings
199
+ + builtin/patch-id: fix type of `get_one_patchid()`
200
+ + builtin/blame: fix type of `length` variable when emitting object ID
201
+ + gpg-interface: address -Wsign-comparison warnings
202
+ + daemon: fix type of `max_connections`
203
+ + daemon: fix loops that have mismatching integer types
204
+ + global: trivial conversions to fix `-Wsign-compare` warnings
205
+ + pkt-line: fix -Wsign-compare warning on 32 bit platform
206
+ + csum-file: fix -Wsign-compare warning on 32-bit platform
207
+ + diff.h: fix index used to loop through unsigned integer
208
+ + config.mak.dev: drop `-Wno-sign-compare`
209
+ + global: mark code units that generate warnings with `-Wsign-compare`
210
+ + compat/win32: fix -Wsign-compare warning in "wWinMain()"
211
+ + compat/regex: explicitly ignore "-Wsign-compare" warnings
212
+ + git-compat-util: introduce macros to disable "-Wsign-compare" warnings
213
+ (this branch is used by ps/the-repository.)
214
+
215
+ Start working to make the codebase buildable with -Wsign-compare.
216
+ source: <20241206-pks-sign-compare-v4-0-0344c6dfb219@pks.im>
217
+
218
+
219
+* ps/ci-gitlab-update (2024-12-12) 4 commits
220
+ (merged to 'next' on 2024-12-15 at e0ca818197)
221
+ + ci/lib: fix "CI setup" sections with GitLab CI
222
+ + ci/lib: do not interpret escape sequences in `group ()` arguments
223
+ + ci/lib: remove duplicate trap to end "CI setup" group
224
+ + gitlab-ci: update macOS images to Sonoma
225
+
226
+ GitLab CI updates.
227
+ source: <20241212-pks-ci-section-fixes-v3-0-d9fe6baee21e@pks.im>
228
+
229
+
230
+* ps/ci-meson (2024-12-13) 10 commits
231
+ (merged to 'next' on 2024-12-17 at fc95a5a9cb)
232
+ + ci: wire up Meson builds
233
+ + t: introduce compatibility options to clar-based tests
234
+ + t: fix out-of-tree tests for some git-p4 tests
235
+ + Makefile: detect missing Meson tests
236
+ + meson: detect missing tests at configure time
237
+ + t/unit-tests: rename clar-based unit tests to have a common prefix
238
+ + Makefile: drop -DSUPPRESS_ANNOTATED_LEAKS
239
+ + ci/lib: support custom output directories when creating test artifacts
240
+ + Merge branch 'ps/build' into ps/ci-meson
241
+ + Merge branch 'cw/worktree-extension' into ps/ci-meson
242
+
243
+ The meson-build procedure is integrated into CI to catch and
244
+ prevent bitrotting.
245
+ cf. <87zfkwgehr.fsf@iotcl.com>
246
+ source: <20241213-pks-meson-ci-v2-0-634affccc694@pks.im>
247
+
248
+
249
+* ps/reftable-alloc-failures-zalloc-fix (2024-12-22) 4 commits
250
+ (merged to 'next' on 2024-12-22 at 92bc55b18e)
251
+ + reftable/basics: return NULL on zero-sized allocations
252
+ + reftable/stack: fix zero-sized allocation when there are no readers
253
+ + reftable/merged: fix zero-sized allocation when there are no readers
254
+ + reftable/stack: don't perform auto-compaction with less than two tables
255
+
256
+ Recent reftable updates mistook a NULL return from a request for
257
+ 0-byte allocation as OOM and died unnecessarily, which has been
258
+ corrected.
259
+ source: <20241222-b4-pks-reftable-oom-fix-without-readers-v2-0-19550090d15a@pks.im>
260
261
262
* sk/calloc-not-malloc-plus-memset (2024-12-18) 1 commit
@@ -216,30 +264,54 @@ Release tarballs are available at:
264
+ git: use calloc instead of malloc + memset where possible
265
266
Code clean-up.
219
-
220
- Will merge to 'master'.
267
source: <pull.1390.v11.git.git.1734540512582.gitgitgadget@gmail.com>
268
269
270
* tb/bitmap-fix-pack-reuse (2024-12-18) 1 commit
225
- - pack-bitmap.c: ensure pack validity for all reuse packs
271
+ (merged to 'next' on 2024-12-21 at 104463402b)
272
+ + pack-bitmap.c: ensure pack validity for all reuse packs
273
274
Code to reuse objects based on bitmap contents have been tightened
275
to avoid race condition even when multiple packs are involved.
229
-
230
- Will merge to 'next'.
276
source: <7fdbfadc04926efc094633b238a55168c92e3d58.1734117577.git.me@ttaylorr.com>
277
278
+--------------------------------------------------
279
+[New Topics]
280
234
-* ps/build-hotfix (2024-12-19) 2 commits
235
- - GIT-VERSION-GEN: fix overriding GIT_BUILT_FROM_COMMIT and GIT_DATE
236
- - GIT-VERSION-GEN: fix overriding version via environment
281
+* jc/show-index-h-update (2024-12-20) 1 commit
282
+ - show-index: the short help should say the command reads from its input
283
238
- source: <20241219-b4-pks-git-version-via-environment-v1-0-9393af058240@pks.im>
284
+ Doc and short-help text for "show-index" has been clarified to
285
+ stress that the command reads its data from the standard input.
286
+
287
+ Comments?
288
+ source: <xmqqfrmidyhk.fsf@gitster.g>
289
290
--------------------------------------------------
291
[Cooking]
292
293
+* ps/the-repository (2024-12-18) 15 commits
294
+ - match-trees: stop using `the_repository`
295
+ - graph: stop using `the_repository`
296
+ - add-interactive: stop using `the_repository`
297
+ - tmp-objdir: stop using `the_repository`
298
+ - resolve-undo: stop using `the_repository`
299
+ - credential: stop using `the_repository`
300
+ - mailinfo: stop using `the_repository`
301
+ - diagnose: stop using `the_repository`
302
+ - server-info: stop using `the_repository`
303
+ - send-pack: stop using `the_repository`
304
+ - serve: stop using `the_repository`
305
+ - trace: stop using `the_repository`
306
+ - pager: stop using `the_repository`
307
+ - progress: stop using `the_repository`
308
+ - Merge branch 'ps/build-sign-compare' into ps/the-repository
309
+
310
+ More code paths have a repository passed through the callchain,
311
+ instead of assuming the primary the_repository object.
312
+ source: <20241217-pks-use-the-repository-conversion-v1-0-0dba48bcc239@pks.im>
313
+
314
+
315
* ps/build-meson-html (2024-12-13) 11 commits
316
- meson: install static files for HTML documentation
317
- meson: generate articles
@@ -256,7 +328,7 @@ Release tarballs are available at:
328
The build procedure based on meson learned to generate HTML
329
documention pages.
330
259
- Needs review.
331
+ Needs review. On hold.
332
source: <20241213-b4-pks-meson-docs-v1-0-0c7895952cd3@pks.im>
333
334
@@ -289,47 +361,6 @@ Release tarballs are available at:
361
source: <20241211-pks-remote-branches-deprecation-v1-0-1431e2369135@pks.im>
362
363
292
-* ps/ci-meson (2024-12-13) 10 commits
293
- (merged to 'next' on 2024-12-17 at fc95a5a9cb)
294
- + ci: wire up Meson builds
295
- + t: introduce compatibility options to clar-based tests
296
- + t: fix out-of-tree tests for some git-p4 tests
297
- + Makefile: detect missing Meson tests
298
- + meson: detect missing tests at configure time
299
- + t/unit-tests: rename clar-based unit tests to have a common prefix
300
- + Makefile: drop -DSUPPRESS_ANNOTATED_LEAKS
301
- + ci/lib: support custom output directories when creating test artifacts
302
- + Merge branch 'ps/build' into ps/ci-meson
303
- + Merge branch 'cw/worktree-extension' into ps/ci-meson
304
-
305
- The meson-build procedure is integrated into CI to catch and
306
- prevent bitrotting.
307
-
308
- Will merge to 'master'.
309
- cf. <87zfkwgehr.fsf@iotcl.com>
310
- source: <20241213-pks-meson-ci-v2-0-634affccc694@pks.im>
311
-
312
-
313
-* kn/reflog-migration (2024-12-16) 9 commits
314
- (merged to 'next' on 2024-12-18 at 5634446b20)
315
- + refs: add support for migrating reflogs
316
- + refs: allow multiple reflog entries for the same refname
317
- + refs: introduce the `ref_transaction_update_reflog` function
318
- + refs: add `committer_info` to `ref_transaction_add_update()`
319
- + refs: extract out refname verification in transactions
320
- + refs/files: add count field to ref_lock
321
- + refs: add `index` field to `struct ref_udpate`
322
- + refs: include committer info in `ref_update` struct
323
- + Merge branch 'kn/reftable-writer-log-write-verify' into kn/reflog-migration
324
- (this branch uses kn/reftable-writer-log-write-verify.)
325
-
326
- "git refs migrate" learned to also migrate the reflog data across
327
- backends.
328
-
329
- Will merge to 'master'.
330
- source: <20241216-320-git-refs-migrate-reflogs-v4-0-d7cd3f197453@gmail.com>
331
-
332
-
364
* cc/lop-remote (2024-12-07) 5 commits
365
. doc: add technical design doc for large object promisors
366
. promisor-remote: check advertised name or URL
@@ -342,83 +373,38 @@ Release tarballs are available at:
373
source: <20241206124248.160494-1-christian.couder@gmail.com>
374
375
345
-* ds/backfill (2024-12-09) 7 commits
346
- - SQUASH??? leakfix
376
+* ds/backfill (2024-12-20) 6 commits
377
- backfill: assume --sparse when sparse-checkout is enabled
378
- backfill: add --sparse option
349
- - backfill: add --batch-size=<n> option
379
+ - backfill: add --min-batch-size=<n> option
380
- backfill: basic functionality and tests
381
- backfill: add builtin boilerplate
382
- Merge branch 'ds/path-walk-1' into ds/backfill
383
(this branch uses ds/path-walk-1.)
384
355
- source: <pull.1820.git.1733515638.gitgitgadget@gmail.com>
356
-
357
-
358
-* kn/reftable-writer-log-write-verify (2024-12-07) 1 commit
359
- (merged to 'next' on 2024-12-15 at 7e6b58d98e)
360
- + reftable/writer: ensure valid range for log's update_index
361
- (this branch is used by kn/reflog-migration.)
362
-
363
- Reftable backend adds check for upper limit of log's update_index.
364
-
365
- Will merge to 'master'.
366
- source: <20241206-424-reftable-writer-add-check-for-limits-v2-1-82ca350b10be@gmail.com>
367
-
368
-
369
-* ps/ci-gitlab-update (2024-12-12) 4 commits
370
- (merged to 'next' on 2024-12-15 at e0ca818197)
371
- + ci/lib: fix "CI setup" sections with GitLab CI
372
- + ci/lib: do not interpret escape sequences in `group ()` arguments
373
- + ci/lib: remove duplicate trap to end "CI setup" group
374
- + gitlab-ci: update macOS images to Sonoma
375
-
376
- GitLab CI updates.
385
+ Lazy-loading missing files in a blobless clone on demand is costly
386
+ as it tends to be one-blob-at-a-time. "git backfill" is introduced
387
+ to help bulk-download necessary files beforehand.
388
378
- Will merge to 'master'.
379
- source: <20241212-pks-ci-section-fixes-v3-0-d9fe6baee21e@pks.im>
389
+ Comments?
390
+ source: <pull.1820.v2.git.1734712193.gitgitgadget@gmail.com>
391
392
393
* re/submodule-parse-opt (2024-12-11) 7 commits
383
- - git-submodule.sh: rename some variables
384
- - git-submodule.sh: improve variables readability
385
- - git-submodule.sh: add some comments
386
- - git-submodule.sh: get rid of unused variable
387
- - git-submodule.sh: get rid of isnumber
388
- - git-submodule.sh: improve parsing of short options
389
- - git-submodule.sh: improve parsing of some long options
394
+ (merged to 'next' on 2024-12-21 at 9e65a56a63)
395
+ + git-submodule.sh: rename some variables
396
+ + git-submodule.sh: improve variables readability
397
+ + git-submodule.sh: add some comments
398
+ + git-submodule.sh: get rid of unused variable
399
+ + git-submodule.sh: get rid of isnumber
400
+ + git-submodule.sh: improve parsing of short options
401
+ + git-submodule.sh: improve parsing of some long options
402
403
"git submodule" learned various ways to spell the same option,
404
e.g. "--branch=B" can be spelled "--branch B" or "-bB".
405
394
- Will merge to 'next'?
395
- source: <20241210184442.10723-1-royeldar0@gmail.com>
396
-
397
-
398
-* ps/build-sign-compare (2024-12-06) 16 commits
399
- (merged to 'next' on 2024-12-16 at 1ddb1485df)
400
- + t/helper: don't depend on implicit wraparound
401
- + scalar: address -Wsign-compare warnings
402
- + builtin/patch-id: fix type of `get_one_patchid()`
403
- + builtin/blame: fix type of `length` variable when emitting object ID
404
- + gpg-interface: address -Wsign-comparison warnings
405
- + daemon: fix type of `max_connections`
406
- + daemon: fix loops that have mismatching integer types
407
- + global: trivial conversions to fix `-Wsign-compare` warnings
408
- + pkt-line: fix -Wsign-compare warning on 32 bit platform
409
- + csum-file: fix -Wsign-compare warning on 32-bit platform
410
- + diff.h: fix index used to loop through unsigned integer
411
- + config.mak.dev: drop `-Wno-sign-compare`
412
- + global: mark code units that generate warnings with `-Wsign-compare`
413
- + compat/win32: fix -Wsign-compare warning in "wWinMain()"
414
- + compat/regex: explicitly ignore "-Wsign-compare" warnings
415
- + git-compat-util: introduce macros to disable "-Wsign-compare" warnings
416
- (this branch is used by ps/the-repository.)
417
-
418
- Start working to make the codebase buildable with -Wsign-compare.
419
-
420
- Will merge to 'master'.
421
- source: <20241206-pks-sign-compare-v4-0-0344c6dfb219@pks.im>
406
+ Will cook in 'next'.
407
+ source: <20241211063234.7610-1-royeldar0@gmail.com>
408
409
410
* tb/unsafe-hash-test (2024-11-21) 2 commits
@@ -483,21 +469,7 @@ Release tarballs are available at:
469
source: <pull.1826.git.git.1730926082.gitgitgadget@gmail.com>
470
471
486
-* js/range-diff-diff-merges (2024-12-16) 3 commits
487
- (merged to 'next' on 2024-12-18 at 47394ea998)
488
- + range-diff: introduce the convenience option `--remerge-diff`
489
- + range-diff: optionally include merge commits' diffs in the analysis
490
- + Merge branch 'js/log-remerge-keep-ancestry' into js/range-diff-diff-merges
491
-
492
- "git range-diff" learned to optionally show and compare merge
493
- commits in the ranges being compared, with the --diff-merges
494
- option.
495
-
496
- Will merge to 'master'.
497
- source: <pull.1734.v3.git.1734358282.gitgitgadget@gmail.com>
498
-
499
-
500
-* ds/name-hash-tweaks (2024-12-03) 8 commits
472
+* ds/name-hash-tweaks (2024-12-20) 8 commits
473
- pack-objects: add third name hash version
474
- pack-objects: prevent name hash version change
475
- test-tool: add helper for name-hash values
@@ -511,10 +483,12 @@ Release tarballs are available at:
483
to use an alternative path-hash function to improve delta-base
484
selection to produce a packfile with deeper history than window
485
size.
514
- source: <pull.1823.v2.git.1733181682.gitgitgadget@gmail.com>
486
487
+ Comments?
488
+ source: <pull.1823.v3.git.1734715194.gitgitgadget@gmail.com>
489
517
-* ds/path-walk-1 (2024-12-07) 7 commits
490
+
491
+* ds/path-walk-1 (2024-12-20) 7 commits
492
- path-walk: reorder object visits
493
- path-walk: mark trees and blobs as UNINTERESTING
494
- path-walk: visit tags and cached objects
@@ -527,19 +501,8 @@ Release tarballs are available at:
501
Introduce a new API to visit objects in batches based on a common
502
path, or by type.
503
530
- Under review.
531
- source: <pull.1818.v3.git.1733514358.gitgitgadget@gmail.com>
532
-
533
-
534
-* as/show-index-uninitialized-hash (2024-11-11) 2 commits
535
- (merged to 'next' on 2024-12-16 at b54e9a56f0)
536
- + t5300: add test for 'show-index --object-format'
537
- + show-index: fix uninitialized hash function
538
-
539
- Regression fix for 'show-index' when run outside of a repository.
540
-
541
- Will merge to 'master'.
542
- source: <20241109092739.14276-1-abhijeet.nkt@gmail.com>
504
+ Comments?
505
+ source: <pull.1818.v4.git.1734711675.gitgitgadget@gmail.com>
506
507
508
* km/config-remote-by-name (2024-10-21) 1 commit