c70fb5fbb0 · matheusbsbs/matheus-bagliano

@@ -1,10 +1,10 @@

1 To: git@vger.kernel.org

2 -Subject: What's cooking in git.git (May 2023, #07; Tue, 23)

3 -X-master-at: 9e49351c3060e1fa6e0d2de64505b7becf157f28

4 -X-next-at: 44b9e1ab91dfc375ef6b0af3df56e45cb118eef8

2 +Subject: What's cooking in git.git (May 2023, #08; Thu, 25)

3 +X-master-at: 79bdd48716a4c455bdc8ffd91d57a18d5cd55baa

4 +X-next-at: 9c6817b8e7dd4f282c873014c94d11929874b708

5 Bcc: lwn@lwn.net, gitster@pobox.com

6

7 -What's cooking in git.git (May 2023, #07; Tue, 23)

7 +What's cooking in git.git (May 2023, #08; Thu, 25)

8 --------------------------------------------------

9

10 Here are the topics that have been cooking in my tree. Commits

@@ -16,12 +16,10 @@ message that raises issues but they are no means exhaustive. A

16 topic without enough support may be discarded after a long period of

17 no activity.

18

19 -Git 2.41-rc1 has been tagged. Thanks for catching and fixing a few

20 -regressions that escaped to the 'master' front so quickly, everybody.

19 +Git 2.41-rc2 has been tagged.

20

22 -Starting next week, until early June, my availability may be

23 -sporadic, but this time I won't be completely away from the keyboard

24 -to require an interrim maintainer.

21 +Until early June, I am on half-vacation, and my bandwidth may be

22 +limited and availability rather sporadic.

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

@@ -52,47 +50,45 @@ Release tarballs are available at:

50 https://www.kernel.org/pub/software/scm/git/

51

52 --------------------------------------------------

55 -[New Topics]

53 +[Graduated to 'master']

54

57 -* jc/test-modernization-2 (2023-05-23) 10 commits

58 - - t9400-git-cvsserver-server: modernize test format

59 - - t9200-git-cvsexportcommit: modernize test format

60 - - t9104-git-svn-follow-parent: modernize test format

61 - - t9100-git-svn-basic: modernize test format

62 - - t7700-repack: modernize test format

63 - - t7600-merge: modernize test format

64 - - t7508-status: modernize test format

65 - - t7201-co: modernize test format

66 - - t7111-reset-table: modernize test format

67 - - t7110-reset-merge: modernize test format

68 - (this branch uses jc/test-modernization.)

55 +* sl/sparse-write-tree-part-2 (2023-05-08) 1 commit

56 + (merged to 'next' on 2023-05-23 at 317fd52454)

57 + + t1092: update a write-tree test

58

70 - Test style updates.

59 + Fix-up to a topic already graduated to 'master'.

60 + source: <20230508202140.464363-1-cheskaqiqi@gmail.com>

61

72 - source: <pull.1514.git.git.1684599239.gitgitgadget@gmail.com>

62 +--------------------------------------------------

63 +[New Topics]

64

65 +* vd/worktree-config-is-per-repository (2023-05-24) 2 commits

66 + - repository: move 'repository_format_worktree_config' to repo scope

67 + - config: use gitdir to get worktree config

68

75 -* jt/path-filter-fix (2023-05-23) 2 commits

76 - - commit-graph: fix murmur3, bump filter ver. to 2

77 - - t4216: test wrong bloom filter version rejection

69 + The value of config.worktree is per-repository, but has been kept

70 + in a singleton global variable per process. This has been OK as

71 + most Git operations interacted with a single repository at a time,

72 + but not right for operations like recursive "grep" that want to

73 + access multiple repositories from a single process without forking.

74

79 - The Bloom filter used for path limited history traversal was broken

80 - on systems whose "char" is unsigned; update the implementation and

81 - bump the format version to 2.

75 + The global variable has been eliminated and made into a member in

76 + the per-repository data structure.

77

78 Needs review.

84 - source: <cover.1684790529.git.jonathantanmy@google.com>

79 + source: <pull.1536.git.1684883872.gitgitgadget@gmail.com>

80

81

87 -* tk/cherry-pick-sequence-requires-clean-worktree (2023-05-23) 1 commit

88 - - cherry-pick: refuse cherry-pick sequence if index is dirty

82 +* tb/submodule-null-deref-fix (2023-05-25) 1 commit

83 + - builtin/submodule--helper.c: handle missing submodule URLs

84

90 - "git cherry-pick A" that replays a single commit stopped before

91 - clobbering local modification, but "git cherry-pick A..B" did not,

92 - which has been corrected.

85 + "git submodule" code trusted the data coming from the config (and

86 + the in-tree .gitmodules file) too much without validating, leading

87 + to NULL dereference if the user mucks with a repository (e.g.

88 + submodule.<name>.url is removed). This has been corrected.

89

94 - Needs review.

95 - source: <pull.1535.git.1684830767336.gitgitgadget@gmail.com>

90 + Will merge to 'next'?

91 + source: <ae6cf3fa461b85e346f034371dae56a2790dfa20.1684957882.git.me@ttaylorr.com>

92

93 --------------------------------------------------

94 [Stalled]

@@ -246,6 +242,48 @@ Release tarballs are available at:

242 --------------------------------------------------

243 [Cooking]

244

245 +* jc/test-modernization-2 (2023-05-23) 10 commits

246 + - t9400-git-cvsserver-server: modernize test format

247 + - t9200-git-cvsexportcommit: modernize test format

248 + - t9104-git-svn-follow-parent: modernize test format

249 + - t9100-git-svn-basic: modernize test format

250 + - t7700-repack: modernize test format

251 + - t7600-merge: modernize test format

252 + - t7508-status: modernize test format

253 + - t7201-co: modernize test format

254 + - t7111-reset-table: modernize test format

255 + - t7110-reset-merge: modernize test format

256 + (this branch uses jc/test-modernization.)

257 +

258 + Test style updates.

259 + source: <pull.1514.git.git.1684599239.gitgitgadget@gmail.com>

260 +

261 +

262 +* jt/path-filter-fix (2023-05-23) 2 commits

263 + - commit-graph: fix murmur3, bump filter ver. to 2

264 + - t4216: test wrong bloom filter version rejection

265 +

266 + The Bloom filter used for path limited history traversal was broken

267 + on systems whose "char" is unsigned; update the implementation and

268 + bump the format version to 2.

269 +

270 + Needs a more careful transition?

271 + cf. <def26c71-0fbb-58a3-f1cd-f8e532b67503@github.com>

272 + source: <cover.1684790529.git.jonathantanmy@google.com>

273 +

274 +

275 +* tk/cherry-pick-sequence-requires-clean-worktree (2023-05-23) 1 commit

276 + - cherry-pick: refuse cherry-pick sequence if index is dirty

277 +

278 + "git cherry-pick A" that replays a single commit stopped before

279 + clobbering local modification, but "git cherry-pick A..B" did not,

280 + which has been corrected.

281 +

282 + Expecting a reroll.

283 + cf. <pull.1535.git.1684830767336.gitgitgadget@gmail.com>

284 + source: <pull.1535.git.1684830767336.gitgitgadget@gmail.com>

285 +

286 +

287 * mh/credential-libsecret-attrs (2023-05-17) 1 commit

288 - credential/libsecret: store new attributes

289

@@ -275,12 +313,13 @@ Release tarballs are available at:

313

314

315 * sl/diff-tree-sparse (2023-05-18) 1 commit

278 - - diff-tree: integrate with sparse index

316 + (merged to 'next' on 2023-05-24 at 5d4f2dec4d)

317 + + diff-tree: integrate with sparse index

318

319 "git diff-tree" has been taught to take advantage of the

320 sparse-index feature.

321

283 - Will merge to 'next'.

322 + Will cook in 'next'.

323 cf. <2a2b7223-bb5d-65f9-95bb-9be45d329c87@github.com>

324 source: <20230518154454.475487-1-cheskaqiqi@gmail.com>

325

@@ -391,13 +430,14 @@ Release tarballs are available at:

430

431

432 * zh/ls-files-format-atoms (2023-05-23) 1 commit

394 - - ls-files: aligin format atoms wtih ls-tree

433 + (merged to 'next' on 2023-05-24 at 116b11effb)

434 + + ls-files: align format atoms with ls-tree

435

436 Some atoms that can be used in "--format=<format>" for "git ls-tree"

437 were not supported by "git ls-files", even though they were relevant

438 in the context of the latter.

439

400 - Will merge to 'next'.

440 + Will cook in 'next'.

441 source: <pull.1533.v2.git.1684832418299.gitgitgadget@gmail.com>

442

443

@@ -583,16 +623,6 @@ Release tarballs are available at:

623 source: <pull.1492.v2.git.1682089074.gitgitgadget@gmail.com>

624

625

586 -* sl/sparse-write-tree-part-2 (2023-05-08) 1 commit

587 - (merged to 'next' on 2023-05-23 at 317fd52454)

588 - + t1092: update a write-tree test

589 -

590 - Fix-up to a topic already graduated to 'master'.

591 -

592 - Will merge to 'master'.

593 - source: <20230508202140.464363-1-cheskaqiqi@gmail.com>

594 -

595 -

626 * tb/pack-bitmap-traversal-with-boundary (2023-05-08) 3 commits

627 - pack-bitmap.c: use commit boundary during bitmap traversal

628 - pack-bitmap.c: extract `fill_in_bitmap()`

What's cooking (2023/05 #08)