6fef827a6b · matheusbsbs/matheus-bagliano

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

1 To: git@vger.kernel.org

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

3 -X-master-at: 79bdd48716a4c455bdc8ffd91d57a18d5cd55baa

4 -X-next-at: 9c6817b8e7dd4f282c873014c94d11929874b708

2 +Subject: What's cooking in git.git (Jun 2023, #01; Thu, 1)

3 +X-master-at: fe86abd7511a9a6862d5706c6fa1d9b57a63ba09

4 +X-next-at: fafddb0af996d6ce627478acb5b2d2c3799d3a0a

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

6

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

7 +What's cooking in git.git (Jun 2023, #01; Thu, 1)

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

9

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

@@ -16,10 +16,7 @@ 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-rc2 has been tagged.

20 -

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

22 -limited and availability rather sporadic.

19 +Git 2.41 (final) has been tagged.

20

21 Copies of the source code to Git live in many repositories, and the

22 following is a list of the ones I push into or their mirrors. Some

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

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

48

49 --------------------------------------------------

53 -[Graduated to 'master']

50 +[New Topics]

51

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

52 +* ds/disable-replace-refs (2023-06-01) 3 commits

53 + - repository: create read_replace_refs setting

54 + - replace-objects: create wrapper around setting

55 + - repository: create disable_replace_refs()

56 + (this branch uses tb/pack-bitmap-traversal-with-boundary.)

57

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

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

58 + Introduce a mechanism to disable replace refs globally and per

59 + repository.

60

62 ---------------------------------------------------

63 -[New Topics]

61 + Will merge to 'next'???

62 + What's the doneness of the base topic?

63 + source: <pull.1537.git.1685126617.gitgitgadget@gmail.com>

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

65

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.

66 +* tz/test-fix-pthreads-prereq (2023-05-26) 1 commit

67 + - trace2 tests: fix PTHREADS prereq

68

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

76 - the per-repository data structure.

69 + Test fix.

70

78 - Needs review.

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

71 + Will merge to 'next'.

72 + source: <20230525031218.3554586-1-tmz@pobox.com>

73

74

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

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

75 +* tz/test-ssh-verifytime-fix (2023-05-26) 1 commit

76 + - t/lib-gpg: fix ssh-keygen -Y check-novalidate with openssh-9.0

77

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.

78 + Test fix.

79

90 - Will merge to 'next'?

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

80 + Will merge to 'next'.

81 + source: <20230525031026.3554406-1-tmz@pobox.com>

82

83 --------------------------------------------------

84 [Stalled]

@@ -242,6 +232,38 @@ Release tarballs are available at:

232 --------------------------------------------------

233 [Cooking]

234

235 +* vd/worktree-config-is-per-repository (2023-05-26) 3 commits

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

237 + - config: pass 'repo' directly to 'config_with_options()'

238 + - config: use gitdir to get worktree config

239 +

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

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

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

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

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

245 +

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

247 + the per-repository data structure.

248 +

249 + Will merge to 'next'???

250 + cf. <3145f4f3-7bd4-8a1b-4943-11b7d22b60c6@github.com>

251 + cf. <kl6lr0qwno2q.fsf@chooglen-macbookpro.roam.corp.google.com>

252 + source: <pull.1536.v2.git.1685064781.gitgitgadget@gmail.com>

253 +

254 +

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

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

257 +

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

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

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

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

262 +

263 + Will merge to 'next'?

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

265 +

266 +

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

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

269 - t9200-git-cvsexportcommit: modernize test format

@@ -272,16 +294,15 @@ Release tarballs are available at:

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

295

296

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

297 +* tk/cherry-pick-sequence-requires-clean-worktree (2023-06-01) 1 commit

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

299

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

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

302 which has been corrected.

303

282 - Expecting a reroll.

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

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

304 + cf. <999f12b2-38d6-f446-e763-4985116ad37d@gmail.com>

305 + source: <pull.1535.v2.git.1685264889088.gitgitgadget@gmail.com>

306

307

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

@@ -308,7 +329,8 @@ Release tarballs are available at:

329

330 Code clean-up.

331

311 - Needs review.

332 + Will merge to 'next'.

333 + cf. <20230519002128.GD2442034@coredump.intra.peff.net>

334 source: <cover.1684324059.git.ps@pks.im>

335

336

@@ -627,11 +649,14 @@ Release tarballs are available at:

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

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

651 - object: add object_array initializer helper function

652 + (this branch is used by ds/disable-replace-refs.)

653

654 The object traversal using reachability bitmap done by

655 "pack-object" has been tweaked to take advantage of the fact that

656 using "boundary" commits as representative of all the uninteresting

657 ones can save quite a lot of object enumeration.

658 +

659 + Comments?

660 source: <cover.1683567065.git.me@ttaylorr.com>

661

662

What's cooking (2023/06 #01)