What's cooking (2020/07 #02)
Junio C Hamano committed
Jul 9, 2020 at 14:36 UTC
06118b88e0965fbc1e2dc34774a641886cbb9181
1 file changed
+189
-321
whats-cooking.txt
+189
-321
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Jul 2020, #01; Mon, 6)
4
-X-master-at: 4a0fcf9f760c9774be77f51e1e88a7499b53d2e2
5
-X-next-at: b3809f4674cea6e2f5db8a478a39b85851690c7d
3
+Subject: What's cooking in git.git (Jul 2020, #02; Thu, 9)
4
+X-master-at: bd42bbe1a46c0fe486fc33e82969275e27e4dc19
5
+X-next-at: f9edc3c819edc268d3a429d06d1efb8fa957866b
6
7
-What's cooking in git.git (Jul 2020, #01; Mon, 6)
7
+What's cooking in git.git (Jul 2020, #02; Thu, 9)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking. Commits prefixed with '-' are
@@ -12,10 +12,11 @@ only in 'seen' (formerly 'pu'---proposed updates) while commits prefixed
12
with '+' are in 'next'. The ones marked with '.' do not appear in any of
13
the integration branches, but I am still holding onto them.
14
15
-We are about to tag the -rc0 "preview" and enter pre-release freeze
16
-period. The change to let users name the initial branch that gets
17
-prepared in a newly created repository has now been merged to be
18
-included in the upcoming release.
15
+The tip of the 'master' branch has been tagged as 'v2.28.0-rc0', as
16
+the preview of upcoming release. From here on, let's focus mostly
17
+on stabilizing what will be in the upcoming 2.28 release and less on
18
+polishing topics not yet in 'next' or starting new ones, so that we
19
+can have a solid release by the end of the month.
20
21
You can find the changes described here in the integration branches of the
22
repositories listed at
@@ -25,228 +26,190 @@ repositories listed at
26
--------------------------------------------------
27
[Graduated to 'master']
28
28
-* ak/commit-graph-to-slab (2020-06-17) 4 commits
29
- (merged to 'next' on 2020-06-25 at 9a10ae18d3)
30
- + commit-graph: minimize commit_graph_data_slab access
31
- + commit: move members graph_pos, generation to a slab
32
- + commit-graph: introduce commit_graph_data_slab
33
- + object: drop parsed_object_pool->commit_count
34
-
35
- A few fields in "struct commit" that do not have to always be
36
- present have been moved to commit slabs.
37
-
38
-
39
-* bc/http-push-flagsfix (2020-06-23) 1 commit
40
- (merged to 'next' on 2020-06-25 at 1dabb1f61b)
41
- + http-push: ensure unforced pushes fail when data would be lost
42
-
43
- The code to push changes over "dumb" HTTP had a bad interaction
44
- with the commit reachability code due to incorrect allocation of
45
- object flag bits, which has been corrected.
46
-
47
-
48
-* bc/sha-256-cvs-svn-updates (2020-06-22) 14 commits
49
- (merged to 'next' on 2020-06-25 at e0d1c87fcf)
50
- + git-cvsexportcommit: port to SHA-256
51
- + git-cvsimport: port to SHA-256
52
- + git-cvsserver: port to SHA-256
53
- + git-svn: set the OID length based on hash algorithm
54
- + perl: make SVN code hash independent
55
- + perl: make Git::IndexInfo work with SHA-256
56
- + perl: create and switch variables for hash constants
57
- + t/lib-git-svn: make hash size independent
58
- + t9101: make hash independent
59
- + t9104: make hash size independent
60
- + t9100: make test work with SHA-256
61
- + t9108: make test hash independent
62
- + t9168: make test hash independent
63
- + t9109: make test hash independent
64
- (this branch uses bc/sha-256-part-2.)
65
-
66
- CVS/SVN interface have been prepared for SHA-256 transition
67
-
68
-
69
-* bc/sha-256-part-2 (2020-06-19) 44 commits
70
- (merged to 'next' on 2020-06-22 at dc153f366d)
71
- + remote-testgit: adapt for object-format
72
- + bundle: detect hash algorithm when reading refs
73
- + t5300: pass --object-format to git index-pack
74
- + t5704: send object-format capability with SHA-256
75
- + t5703: use object-format serve option
76
- + t5702: offer an object-format capability in the test
77
- + t/helper: initialize the repository for test-sha1-array
78
- + remote-curl: avoid truncating refs with ls-remote
79
- + t1050: pass algorithm to index-pack when outside repo
80
- + builtin/index-pack: add option to specify hash algorithm
81
- + remote-curl: detect algorithm for dumb HTTP by size
82
- + builtin/ls-remote: initialize repository based on fetch
83
- + t5500: make hash independent
84
- + serve: advertise object-format capability for protocol v2
85
- + connect: parse v2 refs with correct hash algorithm
86
- + connect: pass full packet reader when parsing v2 refs
87
- + Documentation/technical: document object-format for protocol v2
88
- + t1302: expect repo format version 1 for SHA-256
89
- + builtin/show-index: provide options to determine hash algo
90
- + t5302: modernize test formatting
91
- + packfile: compute and use the index CRC offset
92
- + t3200: mark assertion with SHA1 prerequisite
93
- + setup: set the_repository's hash algo when checking format
94
- + fetch-pack: parse and advertise the object-format capability
95
- + t5562: pass object-format in synthesized test data
96
- + builtin/clone: initialize hash algorithm properly
97
- + remote-curl: implement object-format extensions
98
- + transport-helper: implement object-format extensions
99
- + docs: update remote helper docs for object-format extensions
100
- + builtin/receive-pack: detect when the server doesn't support our hash
101
- + connect: detect algorithm when fetching refs
102
- + fetch-pack: detect when the server doesn't support our hash
103
- + connect: make parse_feature_value extern
104
- + send-pack: detect when the server doesn't support our hash
105
- + connect: add function to detect supported v1 hash functions
106
- + transport: add a hash algorithm member
107
- + pkt-line: add a member for hash algorithm
108
- + connect: add function to fetch value of a v2 server capability
109
- + connect: add function to parse multiple v1 capability values
110
- + remote: advertise the object-format capability on the server side
111
- + wrapper: add function to compare strings with different NUL termination
112
- + connect: have ref processing code take struct packet_reader
113
- + Documentation: document v1 protocol object-format capability
114
- + t1050: match object ID paths in a hash-insensitive way
115
- (this branch is used by bc/sha-256-cvs-svn-updates.)
116
-
117
- SHA-256 migration work continues.
118
-
119
-
120
-* cb/is-descendant-of (2020-06-23) 1 commit
121
- (merged to 'next' on 2020-06-25 at ca0eaddf5e)
122
- + commit-reach: avoid is_descendant_of() shim
123
-
124
- Code clean-up.
125
-
126
-
127
-* dl/test-must-fail-fixes-5 (2020-06-24) 4 commits
128
- (merged to 'next' on 2020-06-29 at efe53a7588)
129
- + lib-submodule-update: pass 'test_must_fail' as an argument
130
- + lib-submodule-update: prepend "git" to $command
131
- + lib-submodule-update: consolidate --recurse-submodules
132
- + lib-submodule-update: add space after function name
133
-
134
- The effort to avoid using test_must_fail on non-git command continues.
135
-
136
-
137
-* en/sparse-status (2020-06-22) 3 commits
138
- (merged to 'next' on 2020-06-25 at 404403a075)
139
- + git-prompt: include sparsity state as well
140
- + git-prompt: document how in-progress operations affect the prompt
141
- + wt-status: show sparse checkout status as well
142
-
143
- "git status" learned to report the status of sparse checkout.
144
-
145
-
146
-* es/get-worktrees-unsort (2020-06-22) 2 commits
147
- (merged to 'next' on 2020-06-25 at 732d93a36d)
148
- + worktree: drop get_worktrees() unused 'flags' argument
149
- + worktree: drop get_worktrees() special-purpose sorting option
150
-
151
- API cleanup for get_worktrees()
152
-
153
-
154
-* es/worktree-code-cleanup (2020-06-24) 1 commit
155
- (merged to 'next' on 2020-06-29 at 91ffd85a31)
156
- + worktree: avoid dead-code in conditional
157
-
158
- Code cleanup.
159
-
160
-
161
-* jk/fast-export-anonym-alt (2020-06-25) 11 commits
162
- (merged to 'next' on 2020-06-29 at 8a8d83e2ca)
163
- + fast-export: use local array to store anonymized oid
164
- + fast-export: anonymize "master" refname
165
- + fast-export: allow seeding the anonymized mapping
166
- + fast-export: add a "data" callback parameter to anonymize_str()
167
- + fast-export: move global "idents" anonymize hashmap into function
168
- + fast-export: use a flex array to store anonymized entries
169
- + fast-export: stop storing lengths in anonymized hashmaps
170
- + fast-export: tighten anonymize_mem() interface to handle only strings
171
- + fast-export: store anonymized oids as hex strings
172
- + fast-export: use xmemdupz() for anonymizing oids
173
- + t9351: derive anonymized tree checks from original repo
29
+* cc/cat-file-usage-update (2020-07-01) 1 commit
30
+ (merged to 'next' on 2020-07-06 at 270769a009)
31
+ + cat-file: add missing [=<format>] to usage/synopsis
32
175
- "git fast-export --anonymize" learned to take customized mapping to
176
- allow its users to tweak its output more usable for debugging.
33
+ Doc/usage update.
34
35
179
-* jl/complete-git-prune (2020-06-22) 1 commit
180
- (merged to 'next' on 2020-06-25 at 64f30b8b41)
181
- + bash-completion: add git-prune into bash completion
36
+* ct/diff-with-merge-base-clarification (2020-07-08) 1 commit
37
+ (merged to 'next' on 2020-07-08 at fc1ab4a479)
38
+ + diff: check for merge bases before assigning sym->base
39
183
- Add "git prune" to the completion (in contrib/), which could be
184
- typed by end-users from the command line.
40
+ Recent update to "git diff" meant as a code clean-up introduced a
41
+ bug in its error handling code, which has been corrected.
42
43
187
-* js/default-branch-name (2020-06-30) 10 commits
188
- (merged to 'next' on 2020-07-01 at c38d766581)
189
- + contrib: subtree: adjust test to change in fmt-merge-msg
190
- (merged to 'next' on 2020-06-25 at 8f962f9219)
191
- + testsvn: respect `init.defaultBranch`
192
- + remote: use the configured default branch name when appropriate
193
- + clone: use configured default branch name when appropriate
194
- + init: allow setting the default for the initial branch name via the config
195
- + init: allow specifying the initial branch name for the new repository
196
- + docs: add missing diamond brackets
197
- + submodule: fall back to remote's HEAD for missing remote.<name>.branch
198
- + send-pack/transport-helper: avoid mentioning a particular branch
199
- + fmt-merge-msg: stop treating `master` specially
44
+* jn/eject-fetch-write-commit-graph-out-of-experimental (2020-07-08) 1 commit
45
+ (merged to 'next' on 2020-07-08 at 1f7cf947f8)
46
+ + experimental: default to fetch.writeCommitGraph=false
47
201
- The name of the primary branch in existing repositories, and the
202
- default name used for the first branch in newly created
203
- repositories, is made configurable, so that we can eventually wean
204
- ourselves off of the hardcoded 'master'.
48
+ "fetch.writeCommitGraph" was enabled when "feature.experimental" is
49
+ asked for, but it was found to be a bit too risky even for bold
50
+ folks in its current shape. The configuration has been ejected, at
51
+ least for now, from the "experimental" feature set.
52
53
207
-* js/diff-files-i-t-a-fix-for-difftool (2020-07-01) 2 commits
208
- (merged to 'next' on 2020-07-01 at cf5d18635c)
209
- + difftool -d: ensure that intent-to-add files are handled correctly
210
- + diff-files --raw: show correct post-image of intent-to-add files
54
+* ma/rebase-doc-typofix (2020-07-09) 1 commit
55
+ (merged to 'next' on 2020-07-09 at 6bf0e26bee)
56
+ + git-rebase.txt: fix description list separator
57
212
- "git difftool" has trouble dealing with paths added to the index
213
- with the intent-to-add bit.
58
+ Typofix.
59
60
216
-* js/pu-to-seen (2020-06-25) 3 commits
217
- (merged to 'next' on 2020-06-25 at 06c9e5a885)
218
- + tests: reference `seen` wherever `pu` was referenced
219
- + docs: adjust the technical overview for the rename `pu` -> `seen`
220
- + docs: adjust for the recent rename of `pu` to `seen`
61
+* mt/entry-fstat-fallback-fix (2020-07-09) 1 commit
62
+ (merged to 'next' on 2020-07-09 at fa0dce39d2)
63
+ + entry: check for fstat() errors after checkout
64
+
65
+ "git checkout" failed to catch an error from fstat() after updating
66
+ a path in the working tree.
67
+
68
+
69
+* ra/send-email-in-reply-to-from-command-line-wins (2020-07-01) 1 commit
70
+ (merged to 'next' on 2020-07-06 at 3892a1ab88)
71
+ + send-email: restore --in-reply-to superseding behavior
72
222
- The documentation and some tests have been adjusted for the recent
223
- renaming of "pu" branch to "seen".
73
+ "git send-email --in-reply-to=<msg>" did not use the In-Reply-To:
74
+ header with the value given from the command line, and let it be
75
+ overridden by the value on In-Reply-To: header in the messages
76
+ being sent out (if exists).
77
78
226
-* mk/pb-pretty-email-without-domain-part-fix (2020-06-23) 1 commit
227
- (merged to 'next' on 2020-06-25 at 81a3aca46b)
228
- + doc: fix author vs. committer copy/paste error
79
+* rs/line-log-until (2020-07-06) 1 commit
80
+ (merged to 'next' on 2020-07-06 at 84d6bc67fa)
81
+ + revision: disable min_age optimization with line-log
82
230
- Docfix.
83
+ "git log -Lx,y:path --before=date" lost track of where the range
84
+ should be because it didn't take the changes made by the youngest
85
+ commits that are omitted from the output into account.
86
87
233
-* ps/ref-transaction-hook (2020-06-19) 1 commit
234
- (merged to 'next' on 2020-06-22 at 3a23dcdbdc)
235
- + refs: implement reference transaction hook
88
+* tb/fix-persistent-shallow (2020-07-08) 1 commit
89
+ (merged to 'next' on 2020-07-08 at ef1709f4bb)
90
+ + commit.c: don't persist substituted parents when unshallowing
91
237
- A new hook.
92
+ When "fetch.writeCommitGraph" configuration is set in a shallow
93
+ repository and a fetch moves the shallow boundary, we wrote out
94
+ broken commit-graph files that do not match the reality, which has
95
+ been corrected.
96
97
240
-* rs/pack-bits-in-object-better (2020-06-24) 1 commit
241
- (merged to 'next' on 2020-06-25 at b3cb296341)
242
- + revision: reallocate TOPO_WALK object flags
98
+* vs/completion-with-set-u (2020-07-01) 1 commit
99
+ (merged to 'next' on 2020-07-06 at 72b1eca511)
100
+ + completion: nounset mode fixes
101
244
- By renumbering object flag bits, "struct object" managed to lose
245
- bloated inter-field padding.
102
+ The command line completion support (in contrib/) used to be
103
+ prepared to work with "set -u" but recent changes got a bit more
104
+ sloppy. This has been corrected.
105
106
--------------------------------------------------
107
[New Topics]
108
109
+* dl/test-must-fail-fixes-6 (2020-07-07) 6 commits
110
+ - test-lib-functions: restrict test_must_fail usage
111
+ - t9400: don't use test_must_fail with cvs
112
+ - t9834: remove use of `test_might_fail p4`
113
+ - t7107: don't use test_must_fail()
114
+ - t5324: reorder `run_with_limited_open_files test_might_fail`
115
+ - t3701: stop using `env` in force_color()
116
+
117
+ Dev support to limit the use of test_must_fail to only git commands.
118
+
119
+
120
+* ds/maintenance (2020-07-07) 21 commits
121
+ - midx: use start_delayed_progress()
122
+ - maintenance: add pack-files auto condition
123
+ - maintenance: create auto condition for loose-objects
124
+ - maintenance: add auto condition for commit-graph task
125
+ - maintenance: use pointers to check --auto
126
+ - maintenance: create maintenance.<task>.enabled config
127
+ - maintenance: auto-size pack-files batch
128
+ - maintenance: add pack-files task
129
+ - maintenance: add loose-objects task
130
+ - maintenance: add fetch task
131
+ - maintenance: take a lock on the objects directory
132
+ - maintenance: add --task option
133
+ - maintenance: add commit-graph task
134
+ - maintenance: initialize task array and hashmap
135
+ - maintenance: replace run_auto_gc()
136
+ - maintenance: add --quiet option
137
+ - maintenance: create basic maintenance runner
138
+ - gc: drop the_repository in log location
139
+ - gc: use repo config
140
+ - gc: use repository in too_many_loose_objects()
141
+ - gc: use the_repository less often
142
+
143
+ A "git gc"'s big brother has been introduced to take care of more
144
+ repository maintenance tasks, not limited to the object database
145
+ cleaning.
146
+
147
+
148
+* jk/t6000-timestamp-fix (2020-07-07) 1 commit
149
+ (merged to 'next' on 2020-07-09 at 633bcd552f)
150
+ + t6000: use test_tick consistently
151
+
152
+ Test update.
153
+
154
+ Will cook in 'next'.
155
+
156
+
157
+* sg/commit-graph-progress-fix (2020-07-09) 2 commits
158
+ (merged to 'next' on 2020-07-09 at 3a9f916ca4)
159
+ + commit-graph: fix "Writing out commit graph" progress counter
160
+ + commit-graph: fix progress of reachable commits
161
+
162
+ The code to produce progress output from "git commit-graph --write"
163
+ had a few breakages, which have been fixed.
164
+
165
+ Will merge to 'master'.
166
+
167
+--------------------------------------------------
168
+[Stalled]
169
+
170
+* dr/push-remoteref-fix (2020-04-23) 1 commit
171
+ - remote.c: fix handling of %(push:remoteref)
172
+
173
+ The "%(push:remoteref)" placeholder in the "--format=" argument of
174
+ "git format-patch" (and friends) only showed what got explicitly
175
+ configured, not what ref at the receiving end would be updated when
176
+ "git push" was used, as it ignored the default behaviour (e.g. update
177
+ the same ref as the source).
178
+
179
+ Expecting a reroll.
180
+ cf. <20200416152145.wp2zeibxmuyas6y6@feanor>
181
+
182
+
183
+* mr/bisect-in-c-2 (2020-07-08) 13 commits
184
+ . bisect--helper: retire `--bisect-autostart` subcommand
185
+ . bisect--helper: retire `--write-terms` subcommand
186
+ . bisect--helper: retire `--check-expected-revs` subcommand
187
+ . bisect--helper: reimplement `bisect_state` & `bisect_head` shell functions in C
188
+ . bisect--helper: retire `--next-all` subcommand
189
+ . bisect--helper: retire `--bisect-clean-state` subcommand
190
+ . bisect--helper: finish porting `bisect_start()` to C
191
+ . bisect--helper: reimplement `bisect_next` and `bisect_auto_next` shell functions in C
192
+ . bisect: call 'clear_commit_marks_all()' in 'bisect_next_all()'
193
+ . bisect--helper: reimplement `bisect_autostart` shell function in C
194
+ . bisect--helper: introduce new `write_in_file()` function
195
+ . bisect--helper: use '-res' in 'cmd_bisect__helper' return
196
+ . bisect--helper: BUG() in cmd_*() on invalid subcommand
197
+
198
+ Rewrite of the remainder of "git bisect" script in C continues.
199
+
200
+ Needs more work.
201
+
202
+
203
+* mk/use-size-t-in-zlib (2018-10-15) 1 commit
204
+ - zlib.c: use size_t for size
205
+
206
+ The wrapper to call into zlib followed our long tradition to use
207
+ "unsigned long" for sizes of regions in memory, which have been
208
+ updated to use "size_t".
209
+
210
+--------------------------------------------------
211
+[Cooking]
212
+
213
* bw/fail-cloning-into-non-empty (2020-07-06) 1 commit
214
- git clone: don't clone into non-empty directory
215
@@ -259,75 +222,50 @@ repositories listed at
222
cf. <xmqqv9j08dxo.fsf@gitster.c.googlers.com>
223
224
262
-* cc/cat-file-usage-update (2020-07-01) 1 commit
263
- (merged to 'next' on 2020-07-06 at 270769a009)
264
- + cat-file: add missing [=<format>] to usage/synopsis
265
-
266
- Doc/usage update.
267
-
268
- Will merge to 'master'.
269
-
270
-
271
-* cc/pretty-contents-size (2020-07-06) 2 commits
272
- - ref-filter: add support for %(contents:size)
273
- - Documentation: clarify %(contents:XXXX) doc
225
+* cc/pretty-contents-size (2020-07-07) 5 commits
226
+ . SQUASH???
227
+ . ref-filter: add support for %(contents:size)
228
+ . t6300: test refs pointing to tree and blob
229
+ . Documentation: clarify 'complete message'
230
+ . Documentation: clarify %(contents:XXXX) doc
231
232
"git for-each-ref --format=<>" learned %(contents:size).
233
234
Expecting a reroll.
278
- with clarified semantics and tests with various object types
279
- cf. <xmqq5zb09v4e.fsf@gitster.c.googlers.com>
235
+ breaks a test on macOS
236
+ cf. <xmqqk0zf3y8s.fsf@gitster.c.googlers.com>
237
238
282
-* ls/mergetool-meld-auto-merge (2020-07-06) 1 commit
283
- - Support auto-merge for meld to follow the vim-diff behavior
239
+* ls/mergetool-meld-auto-merge (2020-07-08) 1 commit
240
+ - mergetool: mergetool: update meld backend to allow using '--auto-merge'
241
242
The 'meld' backend of the "git mergetool" learned to give the
243
underlying 'meld' the '--auto-merge' option, which would help
244
reduce the amount of text that requires manual merging.
245
289
- Expecting a reroll.
290
- with final fixes and readability improvements.
291
- cf. <xmqqzh8c8eda.fsf@gitster.c.googlers.com>
246
293
-
294
-* pb/log-rev-list-doc (2020-07-06) 4 commits
295
- - rev-list-description.txt: fix Asciidoc syntax
247
+* pb/log-rev-list-doc (2020-07-08) 6 commits
248
- git-log.txt: include rev-list-description.txt
249
- git-rev-list.txt: move description to separate file
250
+ - git-rev-list.txt: tweak wording in set operations
251
+ - git-rev-list.txt: fix Asciidoc syntax
252
+ - revisions.txt: describe 'rev1 rev2 ...' meaning for ranges
253
- git-log.txt: add links to 'rev-list' and 'diff' docs
254
255
"git help log" has been enhanced by sharing more material from the
256
documentation for the underlying "git rev-list" command.
257
303
- Expecting a reroll.
304
- with reordering the last one to make it preparatory clean-up.
305
- cf. <xmqqimf087pq.fsf@gitster.c.googlers.com>
306
- cf. <xmqqeepo87hz.fsf@gitster.c.googlers.com>
307
-
308
-
309
-* rs/line-log-until (2020-07-06) 1 commit
310
- (merged to 'next' on 2020-07-06 at 84d6bc67fa)
311
- + revision: disable min_age optimization with line-log
312
-
313
- "git log -Lx,y:path --before=date" lost track of where the range
314
- should be because it didn't take the changes made by the youngest
315
- commits that are omitted from the output into account.
316
-
317
- Will merge to 'master'.
318
-
258
320
-* ta/wait-on-aliased-commands-upon-signal (2020-07-06) 2 commits
321
- - Wait for child on signal death for aliases to externals
322
- - Wait for child on signal death for aliases to builtins
259
+* ta/wait-on-aliased-commands-upon-signal (2020-07-07) 2 commits
260
+ (merged to 'next' on 2020-07-09 at de8bde9182)
261
+ + Wait for child on signal death for aliases to externals
262
+ + Wait for child on signal death for aliases to builtins
263
264
When an aliased command, whose output is piped to a pager by git,
265
gets killed by a signal, the pager got into a funny state, which
266
has been corrected (again).
267
328
- Expecting a reroll.
329
- with improved log messages.
330
- cf. <20200706211403.GB85133@coredump.intra.peff.net>
268
+ Will merge to 'master'.
269
270
271
* tb/upload-pack-filters (2020-07-06) 4 commits
@@ -344,62 +282,6 @@ repositories listed at
282
cf. <cover.1593720075.git.me@ttaylorr.com>
283
284
347
-* vs/completion-with-set-u (2020-07-01) 1 commit
348
- (merged to 'next' on 2020-07-06 at 72b1eca511)
349
- + completion: nounset mode fixes
350
-
351
- The command line completion support (in contrib/) used to be
352
- prepared to work with "set -u" but recent changes got a bit more
353
- sloppy. This has been corrected.
354
-
355
- Will merge to 'master'.
356
-
357
---------------------------------------------------
358
-[Stalled]
359
-
360
-* dr/push-remoteref-fix (2020-04-23) 1 commit
361
- - remote.c: fix handling of %(push:remoteref)
362
-
363
- The "%(push:remoteref)" placeholder in the "--format=" argument of
364
- "git format-patch" (and friends) only showed what got explicitly
365
- configured, not what ref at the receiving end would be updated when
366
- "git push" was used, as it ignored the default behaviour (e.g. update
367
- the same ref as the source).
368
-
369
- Expecting a reroll.
370
- cf. <20200416152145.wp2zeibxmuyas6y6@feanor>
371
-
372
-
373
-* mr/bisect-in-c-2 (2020-04-23) 12 commits
374
- - bisect--helper: retire `--bisect-autostart` subcommand
375
- - bisect--helper: retire `--write-terms` subcommand
376
- - bisect--helper: retire `--check-expected-revs` subcommand
377
- - bisect--helper: reimplement `bisect_state` & `bisect_head` shell functions in C
378
- - bisect--helper: retire `--next-all` subcommand
379
- - bisect--helper: retire `--bisect-clean-state` subcommand
380
- - bisect--helper: finish porting `bisect_start()` to C
381
- - bisect--helper: reimplement `bisect_next` and `bisect_auto_next` shell functions in C
382
- - bisect--helper: reimplement `bisect_autostart` shell function in C
383
- - bisect--helper: introduce new `write_in_file()` function
384
- - bisect--helper: use '-res' in 'cmd_bisect__helper' return
385
- - bisect--helper: fix `cmd_*()` function switch default return
386
-
387
- Rewrite of the remainder of "git bisect" script in C continues.
388
-
389
- Expecting a response to reviews.
390
- cf. <nycvar.QRO.7.76.6.2005230007260.56@tvgsbejvaqbjf.bet>
391
-
392
-
393
-* mk/use-size-t-in-zlib (2018-10-15) 1 commit
394
- - zlib.c: use size_t for size
395
-
396
- The wrapper to call into zlib followed our long tradition to use
397
- "unsigned long" for sizes of regions in memory, which have been
398
- updated to use "size_t".
399
-
400
---------------------------------------------------
401
-[Cooking]
402
-
285
* mt/hash-to-hex-thread-safety (2020-06-26) 2 commits
286
- hex: make hash_to_hex_algop() and friends thread-safe
287
- compat/win32/pthread: add pthread_once()
@@ -423,18 +305,6 @@ repositories listed at
305
Needs tests.
306
307
426
-* ra/send-email-in-reply-to-from-command-line-wins (2020-07-01) 1 commit
427
- (merged to 'next' on 2020-07-06 at 3892a1ab88)
428
- + send-email: restore --in-reply-to superseding behavior
429
-
430
- "git send-email --in-reply-to=<msg>" did not use the In-Reply-To:
431
- header with the value given from the command line, and let it be
432
- overridden by the value on In-Reply-To: header in the messages
433
- being sent out (if exists).
434
-
435
- Will merge to 'master'.
436
-
437
-
308
* ds/commit-graph-bloom-updates (2020-07-01) 10 commits
309
(merged to 'next' on 2020-07-06 at 177e6b362e)
310
+ commit-graph: check all leading directories in changed path Bloom filters
@@ -451,7 +321,7 @@ repositories listed at
321
322
Updates to the changed-paths bloom filter.
323
454
- Will merge to 'master'.
324
+ Will cook in 'next'.
325
326
327
* ss/cmake-build (2020-06-26) 8 commits
@@ -470,6 +340,7 @@ repositories listed at
340
341
342
* sg/commit-graph-cleanups (2020-06-08) 10 commits
343
+ (merged to 'next' on 2020-07-06 at 15c9d77eb9)
344
+ commit-graph: simplify write_commit_graph_file() #2
345
+ commit-graph: simplify write_commit_graph_file() #1
346
+ commit-graph: simplify parse_commit_graph() #2
@@ -485,10 +356,7 @@ repositories listed at
356
The changed-path Bloom filter is improved using ideas from an
357
independent implementation.
358
488
- Under review.
489
- cf. <20200627155610.GN2898@szeder.dev>
490
- cf. <20200627163335.GO2898@szeder.dev>
491
- cf. <20200627155348.GM2898@szeder.dev>
359
+ Will cook in 'next'.
360
361
362
* es/config-hooks (2020-05-21) 4 commits