What's cooking (2022/05 #05)
Junio C Hamano committed
May 16, 2022 at 17:35 UTC
a766380fae4b16cbfb5e2e2643aae6c1f2564cdd
1 file changed
+180
-201
whats-cooking.txt
+180
-201
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (May 2022, #04; Thu, 12)
3
+Subject: What's cooking in git.git (May 2022, #05; Mon, 16)
4
X-master-at: 277cf0bc36094f6dc4297d8c9cef79df045b735d
5
-X-next-at: 0e6072fb45b2316f096b16b5a8b4fee15a93929e
5
+X-next-at: 265bb02f2a67ce96a9eebc26ed274aaae0a30ddb
6
7
-What's cooking in git.git (May 2022, #04; Thu, 12)
7
+What's cooking in git.git (May 2022, #05; Mon, 16)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking in my tree. Commits
@@ -13,23 +13,13 @@ topic is stable enough to be used and are candidate to be in a
13
future release). Commits prefixed with '-' are only in 'seen',
14
and aren't considered "accepted" at all.
15
16
-There unfortunately are still a few regressions whose fixes have
17
-been reviewed but not yet rerolled.
18
-
19
- - hooks no longer is connected directly to the standard output.
20
- cf. <CA+dzEBn108QoMA28f0nC8K21XT+Afua0V2Qv8XkR8rAeqUCCZw@mail.gmail.com>
21
-
22
- - "sudo make install" does not work out-of-the-box.
23
- cf. <4ef9287b-6260-9538-7c89-cffb611520ee@maurel.de>
24
-
25
-With these fixed soon, a new maintenance release needs to follow.
26
-
27
-The tip of 'next' has been rewound and rebuilt, after the remaining
28
-topics that have been cooking in 'next' from the previous cycle have
29
-been flushed to 'master'.
16
+There are too many topics that are marked as "Will merge to next?"
17
+that can use a gentle reminder like "no, the issue raised at $URL
18
+hasn't been resolved yet for that" or "yes, we have discussed it
19
+long and poked at it hard enough and there is no holes".
20
21
This cycle will conclude in early July (https://tinyurl.com/gitCal);
32
-we are in week #3 of the cycle.
22
+we are in week #4 of the cycle.
23
24
Copies of the source code to Git live in many repositories, and the
25
following is a list of the ones I push into or their mirrors. Some
@@ -60,156 +50,89 @@ Release tarballs are available at:
50
https://www.kernel.org/pub/software/scm/git/
51
52
--------------------------------------------------
63
-[Graduated to 'master']
53
+[New Topics]
54
65
-* ab/misc-cleanup (2022-04-01) 6 commits
66
- (merged to 'next' on 2022-04-04 at c5fb674865)
67
- + alloc.[ch]: remove alloc_report() function
68
- + object-store.h: remove unused has_sha1_file*()
69
- + pack-bitmap-write: remove unused bitmap_reset() function
70
- + xdiff/xmacros.h: remove unused XDL_PTRFREE
71
- + configure.ac: remove USE_PIC comment
72
- + run-command.h: remove always unused "clean_on_exit_handler_cbdata"
55
+* tb/midx-race-in-pack-objects (2022-05-13) 2 commits
56
+ - builtin/pack-objects.c: ensure pack validity from MIDX bitmap objects
57
+ - pack-bitmap: check preferred pack validity when opening MIDX bitmap
58
74
- Code clean-up.
75
- source: <cover-v4-0.6-00000000000-20220331T014349Z-avarab@gmail.com>
59
+ The multi-pack-index code did not protect the packfile it is going
60
+ to depend on from getting removed while in use, which has been
61
+ corrected.
62
63
+ Will merge to 'next'?
64
+ source: <cover.1652458395.git.me@ttaylorr.com>
65
78
-* ah/rebase-keep-base-fix (2022-04-21) 1 commit
79
- (merged to 'next' on 2022-05-02 at 8e6071e208)
80
- + rebase: use correct base for --keep-base when a branch is given
66
82
- "git rebase --keep-base <upstream> <branch-to-rebase>" computed the
83
- commit to rebase onto incorrectly, which has been corrected.
84
- source: <20220421044233.894255-1-alexhenrie24@gmail.com>
67
+* ds/bundle-uri (2022-05-16) 8 commits
68
+ - bundle.h: make "fd" version of read_bundle_header() public
69
+ - remote: allow relative_url() to return an absolute url
70
+ - remote: move relative_url()
71
+ - http: make http_get_file() external
72
+ - fetch-pack: move --keep=* option filling to a function
73
+ - fetch-pack: add a deref_without_lazy_fetch_extended()
74
+ - dir API: add a generalized path_match_flags() function
75
+ - connect.c: refactor sending of agent & object-format
76
77
+ source: <pull.1233.git.1652731865.gitgitgadget@gmail.com>
78
87
-* ea/progress-partial-blame (2022-04-06) 1 commit
88
- (merged to 'next' on 2022-04-07 at 7df8392d71)
89
- + blame: report correct number of lines in progress when using ranges
79
91
- The progress meter of "git blame" was showing incorrect numbers
92
- when processing only parts of the file.
93
- source: <20220406181320.16911-1-eantoranz@gmail.com>
80
+* ds/sparse-sparse-checkout (2022-05-16) 8 commits
81
+ - sparse-checkout: integrate with sparse index
82
+ - p2000: add test for 'git sparse-checkout [add|set]'
83
+ - sparse-index: complete partial expansion
84
+ - sparse-index: partially expand directories
85
+ - sparse-checkout: --no-sparse-index needs a full index
86
+ - cache-tree: implement cache_tree_find_path()
87
+ - sparse-index: introduce partially-sparse indexes
88
+ - sparse-index: create expand_to_pattern_list()
89
90
+ "sparse-checkout" learns to work well with the sparse-index
91
+ feature.
92
+ source: <pull.1208.git.1652724693.gitgitgadget@gmail.com>
93
96
-* ea/rebase-code-simplify (2022-04-20) 1 commit
97
- (merged to 'next' on 2022-05-02 at 88ed49c2d0)
98
- + rebase: simplify an assignment of options.type in cmd_rebase
94
100
- Code clean-up.
101
- source: <20220418172721.215898-1-eantoranz@gmail.com>
102
-
103
-
104
-* fr/vimdiff-layout (2022-04-03) 4 commits
105
- (merged to 'next' on 2022-04-04 at 5d1c8197d0)
106
- + mergetools: add description to all diff/merge tools
107
- + vimdiff: add tool documentation
108
- + vimdiff: integrate layout tests in the unit tests framework ('t' folder)
109
- + vimdiff: new implementation with layout support
110
-
111
- Reimplement "vimdiff[123]" mergetool drivers with a more generic
112
- layout mechanism.
113
- source: <20220330191909.294610-1-greenfoo@u92.eu>
114
-
115
-
116
-* jh/p4-various-fixups (2022-04-01) 22 commits
117
- (merged to 'next' on 2022-04-04 at 251b14976f)
118
- + git-p4: sort imports
119
- + git-p4: seperate multiple statements onto seperate lines
120
- + git-p4: move inline comments to line above
121
- + git-p4: only seperate code blocks by a single empty line
122
- + git-p4: compare to singletons with "is" and "is not"
123
- + git-p4: normalize indentation of lines in conditionals
124
- + git-p4: ensure there is a single space around all operators
125
- + git-p4: ensure every comment has a single #
126
- + git-p4: remove spaces between dictionary keys and colons
127
- + git-p4: remove redundant backslash-continuations inside brackets
128
- + git-p4: remove extraneous spaces before function arguments
129
- + git-p4: place a single space after every comma
130
- + git-p4: removed brackets when assigning multiple return values
131
- + git-p4: remove spaces around default arguments
132
- + git-p4: remove padding from lists, tuples and function arguments
133
- + git-p4: sort and de-duplcate pylint disable list
134
- + git-p4: remove commented code
135
- + git-p4: convert descriptive class and function comments into docstrings
136
- + git-p4: improve consistency of docstring formatting
137
- + git-p4: indent with 4-spaces
138
- + git-p4: remove unneeded semicolons from statements
139
- + git-p4: add blank lines between functions and class definitions
140
-
141
- Various cleanups to "git p4".
142
- source: <20220401142504.58995-1-jholdsworth@nvidia.com>
143
-
144
-
145
-* kt/commit-graph-plug-fp-leak-on-error (2022-04-20) 1 commit
146
- (merged to 'next' on 2022-05-02 at c3bcb92518)
147
- + commit-graph: close file before returning NULL
148
-
149
- Fix a leak of FILE * in an error codepath.
150
- source: <pull.1213.git.1650302007395.gitgitgadget@gmail.com>
151
-
152
-
153
-* pw/test-malloc-with-sanitize-address (2022-04-11) 1 commit
154
- (merged to 'next' on 2022-05-02 at a25766055f)
155
- + tests: make SANITIZE=address imply TEST_NO_MALLOC_CHECK
156
-
157
- Avoid problems from interaction between malloc_check and address
158
- sanitizer.
159
- source: <pull.1210.git.1649507317350.gitgitgadget@gmail.com>
160
-
161
-
162
-* rs/commit-summary-wo-break-rewrite (2022-04-06) 1 commit
163
- (merged to 'next' on 2022-05-02 at c40509b820)
164
- + commit, sequencer: turn off break_opt for commit summary
165
-
166
- The commit summary shown after making a commit is matched to what
167
- is given in "git status" not to use the break-rewrite heuristics.
168
- source: <c35bd0aa-2e46-e710-2b39-89f18bad0097@web.de>
169
-
170
-
171
-* tk/untracked-cache-with-uall (2022-04-01) 2 commits
172
- (merged to 'next' on 2022-04-04 at 2e11f1ac0c)
173
- + untracked-cache: support '--untracked-files=all' if configured
174
- + untracked-cache: test untracked-cache-bypassing behavior with -uall
175
-
176
- The performance of the "untracked cache" feature has been improved
177
- when "--untracked-files=<mode>" and "status.showUntrackedFiles"
178
- are combined.
179
- source: <pull.985.v6.git.1648742535.gitgitgadget@gmail.com>
95
+* gc/bare-repo-discovery (2022-05-16) 3 commits
96
+ - SQUASH??? move new test to t0035
97
+ - setup.c: learn discovery.bareRepository=cwd
98
+ - setup.c: make bare repo discovery optional
99
181
---------------------------------------------------
182
-[New Topics]
100
+ Introduce a discovery.barerepository configuration variable that
101
+ allows users to forbid discovery of bare repositories.
102
184
-* gg/worktree-from-the-above (2022-05-11) 2 commits
185
- - dir: minor refactoring / clean-up
186
- - dir: consider worktree config in path recursion
103
+ Expecting a reroll.
104
+ source: <pull.1261.v2.git.git.1652485058.gitgitgadget@gmail.com>
105
188
- With a non-bare repository, with core.worktree pointing at a
189
- directory that has the repository as its subdirectory, regressed in
190
- Git 2.27 days.
106
192
- Expecting a reroll.
193
- source: <20220510171527.25778-1-ggossdev@gmail.com>
107
+* jt/fetch-peek-optional-section (2022-05-16) 1 commit
108
+ - fetch-pack: make unexpected peek result non-fatal
109
110
+ "git fetch" unnecessarily failed when an unexpected optional
111
+ section appeared in the output, which has been corrected.
112
196
-* jc/update-ozlabs-url (2022-05-11) 1 commit
197
- (merged to 'next' on 2022-05-12 at d6b14040b6)
198
- + SubmittingPatches: use more stable git.ozlabs.org URL
113
+ Will merge to 'next'.
114
+ source: <20220516110221.3490982-1-jonathantanmy@google.com>
115
200
- Will merge to 'master'.
116
117
+* os/fetch-check-not-current-branch (2022-05-16) 1 commit
118
+ - fetch: limit shared symref check only for local branches
119
203
-* jc/archive-add-file-normalize-mode (2022-05-12) 1 commit
204
- - archive: do not let on-disk mode leak to zip archives
120
+ The way "git fetch" without "--update-head-ok" ensures that HEAD in
121
+ no worktree points at any ref being updated was too wasteful, which
122
+ has been optimized a bit.
123
206
- "git archive --add-file=<path>" picked up the raw permission bits
207
- from the path and propagated to zip output in some cases, without
208
- normalization, which has been corrected (tar output did not have
209
- this issue).
124
+ Will merge to 'next'?
125
+ source: <pull.1266.v2.git.git.1652690501963.gitgitgadget@gmail.com>
126
+
127
+
128
+* ds/object-file-unpack-loose-header-fix (2022-05-16) 1 commit
129
+ - object-file: convert 'switch' back to 'if'
130
+ (this branch uses ab/valgrind-fixes.)
131
+
132
+ Coding style fix.
133
134
Will merge to 'next'?
212
- source: <xmqqmtfme8v6.fsf@gitster.g>
135
+ source: <377be0e9-8a0f-4a86-0a66-3b08c0284dae@github.com>
136
137
--------------------------------------------------
138
[Stalled]
@@ -354,25 +277,60 @@ Release tarballs are available at:
277
--------------------------------------------------
278
[Cooking]
279
280
+* gg/worktree-from-the-above (2022-05-11) 2 commits
281
+ - dir: minor refactoring / clean-up
282
+ - dir: consider worktree config in path recursion
283
+
284
+ With a non-bare repository, with core.worktree pointing at a
285
+ directory that has the repository as its subdirectory, regressed in
286
+ Git 2.27 days.
287
+
288
+ Expecting a reroll.
289
+ source: <20220510171527.25778-1-ggossdev@gmail.com>
290
+
291
+
292
+* jc/update-ozlabs-url (2022-05-11) 1 commit
293
+ (merged to 'next' on 2022-05-12 at d6b14040b6)
294
+ + SubmittingPatches: use more stable git.ozlabs.org URL
295
+
296
+ Will merge to 'master'.
297
+
298
+
299
+* jc/archive-add-file-normalize-mode (2022-05-12) 1 commit
300
+ (merged to 'next' on 2022-05-16 at 265bb02f2a)
301
+ + archive: do not let on-disk mode leak to zip archives
302
+
303
+ "git archive --add-file=<path>" picked up the raw permission bits
304
+ from the path and propagated to zip output in some cases, without
305
+ normalization, which has been corrected (tar output did not have
306
+ this issue).
307
+
308
+ Will merge to 'master'.
309
+ source: <xmqqmtfme8v6.fsf@gitster.g>
310
+
311
+
312
* ab/commit-plug-leaks (2022-05-12) 1 commit
358
- - commit: fix "author_ident" leak
313
+ (merged to 'next' on 2022-05-16 at 00bcda44af)
314
+ + commit: fix "author_ident" leak
315
316
Leakfix in the top-level called-once function.
317
362
- Will merge to 'next'?
318
+ Will merge to 'master'.
319
source: <xmqqzgjmcqlg.fsf@gitster.g>
320
321
322
* ab/valgrind-fixes (2022-05-12) 4 commits
367
- - commit-graph.c: don't assume that stat() succeeds
368
- - object-file: fix a unpack_loose_header() regression in 3b6a8db3b03
369
- - log test: skip a failing mkstemp() test under valgrind
370
- - tests: using custom GIT_EXEC_PATH breaks --valgrind tests
323
+ (merged to 'next' on 2022-05-16 at 75d760528f)
324
+ + commit-graph.c: don't assume that stat() succeeds
325
+ + object-file: fix a unpack_loose_header() regression in 3b6a8db3b03
326
+ + log test: skip a failing mkstemp() test under valgrind
327
+ + tests: using custom GIT_EXEC_PATH breaks --valgrind tests
328
+ (this branch is used by ds/object-file-unpack-loose-header-fix.)
329
330
A bit of test framework fixes with a few fixes to issues found by
331
valgrind.
332
375
- Will merge to 'next'?
333
+ Will merge to 'master'.
334
source: <20220512223218.237544-1-gitster@pobox.com>
335
336
@@ -415,10 +373,12 @@ Release tarballs are available at:
373
374
"git remote -v" now shows the list-objects-filter used during
375
fetching from the remote, if available.
376
+
377
+ Will merge to 'next'?
378
source: <pull.1227.v4.git.1652095969026.gitgitgadget@gmail.com>
379
380
421
-* cc/http-curlopt-resolve (2022-05-09) 1 commit
381
+* cc/http-curlopt-resolve (2022-05-16) 1 commit
382
- http: add custom hostname to IP address resolutions
383
384
With the new http.curloptResolve configuration, the CURLOPT_RESOLVE
@@ -426,7 +386,7 @@ Release tarballs are available at:
386
IP addresses for the requests is exposed to the scripts.
387
388
Will merge to 'next'?
429
- source: <20220509153834.485871-1-chriscool@tuxfamily.org>
389
+ source: <20220516083851.202057-1-chriscool@tuxfamily.org>
390
391
392
* js/trace2-doc-fixes (2022-05-04) 6 commits
@@ -462,53 +422,58 @@ Release tarballs are available at:
422
423
424
* tk/p4-metadata-coding-strategies (2022-05-04) 1 commit
465
- - git-p4: improve encoding handling to support inconsistent encodings
425
+ (merged to 'next' on 2022-05-13 at d083cc3ff0)
426
+ + git-p4: improve encoding handling to support inconsistent encodings
427
428
"git p4" updates.
429
469
- Will merge to 'next'?
430
+ Will merge to 'master'.
431
source: <pull.1206.v4.git.1651346812586.gitgitgadget@gmail.com>
432
433
434
* ep/equals-null-cocci (2022-05-02) 2 commits
474
- - tree-wide: apply equals-null.cocci
475
- - Merge branch 'ep/maint-equals-null-cocci' into ep/equals-null-cocci
435
+ (merged to 'next' on 2022-05-13 at a8de51ce7a)
436
+ + tree-wide: apply equals-null.cocci
437
+ + Merge branch 'ep/maint-equals-null-cocci' into ep/equals-null-cocci
438
(this branch uses ep/maint-equals-null-cocci.)
439
440
Merges up ep/maint-equals-null-cocci to the current codebase.
441
480
- Will merge to 'next'.
442
+ Will merge to 'master'.
443
444
445
* ep/maint-equals-null-cocci (2022-05-02) 4 commits
484
- - tree-wide: apply equals-null.cocci
485
- - Merge branch 'ep/maint-equals-null-cocci' for maint-2.35
486
- - tree-wide: apply equals-null.cocci
487
- - contrib/coccinnelle: add equals-null.cocci
446
+ (merged to 'next' on 2022-05-13 at 022e914848)
447
+ + tree-wide: apply equals-null.cocci
448
+ + Merge branch 'ep/maint-equals-null-cocci' for maint-2.35
449
+ + tree-wide: apply equals-null.cocci
450
+ + contrib/coccinnelle: add equals-null.cocci
451
(this branch is used by ep/equals-null-cocci.)
452
453
Introduce and apply coccinelle rule to discourage an explicit
454
comparison between a pointer and NULL, and applies the clean-up to
455
the maintenance track.
456
494
- Will merge to 'next'.
457
+ Will merge to 'master'.
458
459
460
* ds/sparse-colon-path (2022-04-26) 5 commits
498
- - rev-parse: integrate with sparse index
499
- - object-name: diagnose trees in index properly
500
- - object-name: reject trees found in the index
501
- - show: integrate with the sparse index
502
- - t1092: add compatibility tests for 'git show'
461
+ (merged to 'next' on 2022-05-13 at f1740d248a)
462
+ + rev-parse: integrate with sparse index
463
+ + object-name: diagnose trees in index properly
464
+ + object-name: reject trees found in the index
465
+ + show: integrate with the sparse index
466
+ + t1092: add compatibility tests for 'git show'
467
468
"git show :<path>" learned to work better with the sparse-index
469
feature.
470
507
- Will merge to 'next'.
471
+ Will merge to 'master'.
472
source: <pull.1207.v2.git.1651005800.gitgitgadget@gmail.com>
473
474
511
-* cb/path-owner-check-with-sudo (2022-05-10) 3 commits
475
+* cb/path-owner-check-with-sudo (2022-05-12) 4 commits
476
+ - git-compat-util: allow root to access both SUDO_UID and root owned
477
- t0034: add negative tests and allow git init to mostly work under sudo
478
- git-compat-util: avoid failing dir ownership checks if running privileged
479
- t: regression git needs safe.directory when using sudo
@@ -519,10 +484,10 @@ Release tarballs are available at:
484
the safety.
485
486
Will merge to 'next'?
522
- source: <20220510174616.18629-1-carenas@gmail.com>
487
+ source: <20220513010020.55361-1-carenas@gmail.com>
488
489
525
-* pb/ggg-in-mfc-doc (2022-05-10) 5 commits
490
+* pb/ggg-in-mfc-doc (2022-05-12) 5 commits
491
- MyFirstContribution: drop PR description for GGG single-patch contributions
492
- MyFirstContribution: reference "The cover letter" in GitGitGadget section
493
- MyFirstContribution: reference "The cover letter" in "Preparing Email"
@@ -531,9 +496,8 @@ Release tarballs are available at:
496
497
Documentation update.
498
534
- Expecting a reroll.
535
- cf. <a955b9f1-3e11-70c5-b390-a35b420d6835@gmail.com>
536
- source: <pull.1226.v2.git.1652233654.gitgitgadget@gmail.com>
499
+ Will merge to 'next'?
500
+ source: <pull.1226.v3.git.1652399017.gitgitgadget@gmail.com>
501
502
503
* sg/safe-directory-tests-and-docs (2022-04-27) 3 commits
@@ -553,22 +517,23 @@ Release tarballs are available at:
517
518
A new doc that lists tips for tools to work with Git's codebase.
519
556
- Thoughts?
520
+ Will merge to 'next'?
521
source: <20220421084515.21236-2-cogoni.guillaume@gmail.com>
522
523
524
* cb/ci-make-p4-optional (2022-05-12) 4 commits
561
- - ci: use https, not http to download binaries from perforce.com
562
- - ci: reintroduce prevention from perforce being quarantined in macOS
563
- - ci: avoid brew for installing perforce
564
- - ci: make failure to find perforce more user friendly
525
+ (merged to 'next' on 2022-05-13 at 7e84679e2a)
526
+ + ci: use https, not http to download binaries from perforce.com
527
+ + ci: reintroduce prevention from perforce being quarantined in macOS
528
+ + ci: avoid brew for installing perforce
529
+ + ci: make failure to find perforce more user friendly
530
531
macOS CI jobs have been occasionally flaky due to tentative version
532
skew between perforce and the homebrew packager. Instead of
533
failing the whole CI job, just let it skip the p4 tests when this
534
happens.
535
571
- Will merge to 'next'?
536
+ Will merge to 'master'.
537
source: <20220512223940.238367-1-gitster@pobox.com>
538
539
@@ -578,6 +543,8 @@ Release tarballs are available at:
543
The "--current" option of "git show-branch" should have been made
544
incompatible with the "--reflog" mode, but this was not enforced,
545
which has been corrected.
546
+
547
+ Will merge to 'next'.
548
source: <xmqqh76mf7s4.fsf_-_@gitster.g>
549
550
@@ -599,6 +566,12 @@ Release tarballs are available at:
566
"git send-email" is changed so that by default it asks for
567
confirmation before sending each message out.
568
569
+ Will discard.
570
+
571
+ I wanted to like this, and had it in the version of Git I use
572
+ myself for daily work, but the prompting turned out to be somewhat
573
+ distracting.
574
+
575
Thoughts?
576
source: <20220422083629.1404989-1-hi@alyssa.is>
577
@@ -628,16 +601,17 @@ Release tarballs are available at:
601
602
603
* vd/sparse-stash (2022-05-10) 6 commits
631
- - unpack-trees: preserve index sparsity
632
- - stash: apply stash using 'merge_ort_nonrecursive()'
633
- - read-cache: set sparsity when index is new
634
- - sparse-index: expose 'is_sparse_index_allowed()'
635
- - stash: integrate with sparse index
636
- - stash: expand sparse-checkout compatibility testing
604
+ (merged to 'next' on 2022-05-13 at 0f52519a0e)
605
+ + unpack-trees: preserve index sparsity
606
+ + stash: apply stash using 'merge_ort_nonrecursive()'
607
+ + read-cache: set sparsity when index is new
608
+ + sparse-index: expose 'is_sparse_index_allowed()'
609
+ + stash: integrate with sparse index
610
+ + stash: expand sparse-checkout compatibility testing
611
612
Teach "git stash" to work better with sparse index entries.
613
640
- Will merge to 'next'?
614
+ Will merge to 'master'.
615
source: <pull.1171.v3.git.1652225552.gitgitgadget@gmail.com>
616
617
@@ -654,6 +628,10 @@ Release tarballs are available at:
628
* ep/coverage-report-wants-test-to-have-run (2022-04-13) 1 commit
629
- Makefile: add a prerequisite to the coverage-report target
630
631
+ "make coverage-report" without first running "make coverage" did
632
+ not produce any meaningful result, which has been corrected.
633
+
634
+ Will merge to 'next'.
635
source: <20220414022513.31465-1-gitter.spiros@gmail.com>
636
637
@@ -859,7 +837,7 @@ Release tarballs are available at:
837
838
"git p4" update.
839
862
- Will merge to 'next'?
840
+ Will merge to 'master'.
841
source: <pull.1180.git.1647866603032.gitgitgadget@gmail.com>
842
843
@@ -887,19 +865,20 @@ Release tarballs are available at:
865
866
867
* en/sparse-cone-becomes-default (2022-04-21) 9 commits
890
- - Documentation: some sparsity wording clarifications
891
- - git-sparse-checkout.txt: mark non-cone mode as deprecated
892
- - git-sparse-checkout.txt: flesh out pattern set sections a bit
893
- - git-sparse-checkout.txt: add a new EXAMPLES section
894
- - git-sparse-checkout.txt: shuffle some sections and mark as internal
895
- - git-sparse-checkout.txt: update docs for deprecation of 'init'
896
- - git-sparse-checkout.txt: wording updates for the cone mode default
897
- - sparse-checkout: make --cone the default
898
- - tests: stop assuming --no-cone is the default mode for sparse-checkout
868
+ (merged to 'next' on 2022-05-13 at c168eb55cf)
869
+ + Documentation: some sparsity wording clarifications
870
+ + git-sparse-checkout.txt: mark non-cone mode as deprecated
871
+ + git-sparse-checkout.txt: flesh out pattern set sections a bit
872
+ + git-sparse-checkout.txt: add a new EXAMPLES section
873
+ + git-sparse-checkout.txt: shuffle some sections and mark as internal
874
+ + git-sparse-checkout.txt: update docs for deprecation of 'init'
875
+ + git-sparse-checkout.txt: wording updates for the cone mode default
876
+ + sparse-checkout: make --cone the default
877
+ + tests: stop assuming --no-cone is the default mode for sparse-checkout
878
879
Deprecate non-cone mode of the sparse-checkout feature.
880
902
- Will merge to 'next'.
881
+ Will cook in 'next' til 06-03 and then merge to 'master'.
882
source: <pull.1148.v3.git.1650594746.gitgitgadget@gmail.com>
883
884
@@ -942,7 +921,7 @@ Release tarballs are available at:
921
branch $A at the remote $B came from. Also more places use the
922
sole remote, if exists, before defaulting to 'origin'.
923
945
- Thoughts?
924
+ Will merge to 'next'?
925
source: <pull.1161.v5.git.1651226206.gitgitgadget@gmail.com>
926
927