What's coking (2019/10 #07)
Junio C Hamano committed
Oct 30, 2019 at 16:11 UTC
56c132a335048b35ce1a2521955c6fde3e333880
1 file changed
+241
-190
whats-cooking.txt
+241
-190
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (Oct 2019, #06; Thu, 24)
4
-X-master-at: 566a1439f6f56c2171b8853ddbca0ad3f5098770
5
-X-next-at: b1bccd3e3df55f279f5b5f202ffa7149543587de
3
+Subject: What's cooking in git.git (Oct 2019, #07; Wed, 30)
4
+X-master-at: f21f8f5d35b09ecdd1a0112f114436fd2eda7df2
5
+X-next-at: 50e10028f102536c1a9ac2647d3aae9cc8a7c5d7
6
7
-What's cooking in git.git (Oct 2019, #06; Thu, 24)
7
+What's cooking in git.git (Oct 2019, #07; Wed, 30)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking. Commits prefixed with
@@ -12,10 +12,9 @@ Here are the topics that have been cooking. Commits prefixed with
12
'+' 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
-The first release candidate has been tagged on the 'master' front.
16
-We probably would want to include ds/commit-graph-on-fetch fixup
17
-(which is not in 'next' yet) in the upcoming release, but other than
18
-that, this should be very close to the final one, I hope ;-)
15
+There is the v2.24.0-rc2 tag now; the contents of the release
16
+candidate hasn't changed much since the -rc1; hopefully we can see
17
+the final thing real soon now.
18
19
You can find the changes described here in the integration branches
20
of the repositories listed at
@@ -25,100 +24,215 @@ of the repositories listed at
24
--------------------------------------------------
25
[Graduated to "master"]
26
28
-* bc/smart-http-atomic-push (2019-10-17) 1 commit
29
- (merged to 'next' on 2019-10-18 at 7729d13f51)
30
- + remote-curl: pass on atomic capability to remote side
27
+* js/mingw-needs-hiding-fix (2019-10-28) 1 commit
28
+ (merged to 'next' on 2019-10-28 at d41210960f)
29
+ + mingw: avoid a buffer overrun in `needs_hiding()`
30
32
- The atomic push over smart HTTP transport did not work, which has
33
- been corrected.
31
+ Fix for a (rather old) buffer-overrun bug.
32
+
33
+
34
+* rl/gitweb-blame-prev-fix (2019-10-28) 1 commit
35
+ (merged to 'next' on 2019-10-28 at 876152daa8)
36
+ + gitweb: correctly store previous rev in javascript-actions mode
37
+
38
+ Fix a rather old bug in gitweb---incremental blame output in
39
+ javascript actions mode never worked.
40
+
41
+
42
+* wb/fsmonitor-bitmap-fix (2019-10-30) 1 commit
43
+ (merged to 'next' on 2019-10-30 at f63ada9e8d)
44
+ + t7519-status-fsmonitor: improve comments
45
+
46
+ Comment update.
47
+
48
+--------------------------------------------------
49
+[New Topics]
50
+
51
+* en/doc-typofix (2019-10-25) 1 commit
52
+ (merged to 'next' on 2019-10-30 at 8405cac984)
53
+ + Documentation: fix a bunch of typos, both old and new
54
+
55
+ Docfix.
56
+
57
+ Will cook in 'next'.
58
+
59
+
60
+* hw/remove-api-docs-placeholder (2019-10-25) 1 commit
61
+ (merged to 'next' on 2019-10-30 at c99fe16682)
62
+ + documentation: remove empty doc files
63
+
64
+ Docfix.
65
+
66
+ Will cook in 'next'.
67
+
68
+
69
+* js/update-index-ignore-removal-for-skip-worktree (2019-10-29) 2 commits
70
+ (merged to 'next' on 2019-10-30 at 5c7c7a6055)
71
+ + stash: handle staged changes in skip-worktree files correctly
72
+ + update-index: optionally leave skip-worktree entries alone
73
+
74
+ "git stash save" in a working tree that is sparsely checked out
75
+ mistakenly removed paths that are outside the area of interest.
76
+
77
+ Will cook in 'next'.
78
+
79
+
80
+* pb/pretty-email-without-domain-part (2019-10-30) 3 commits
81
+ (merged to 'next' on 2019-10-30 at 06f719efa5)
82
+ + pretty: add "%aL" etc. to show local-part of email addresses
83
+ + t4203: use test-lib.sh definitions
84
+ + t6006: use test-lib.sh definitions
85
+
86
+ The custom format for "git log --format=<format>" learned the l/L
87
+ placeholder that is similar to e/E that fills in the e-mail
88
+ address, but only the local part on the left side of '@'.
89
+
90
+ Will cook in 'next'.
91
92
36
-* bw/format-patch-o-create-leading-dirs (2019-10-23) 1 commit
37
- (merged to 'next' on 2019-10-23 at 9204e1b2b9)
38
- + t4014: make output-directory tests self-contained
93
+* sg/commit-graph-usage-fix (2019-10-28) 1 commit
94
+ (merged to 'next' on 2019-10-28 at 13d01506dd)
95
+ + builtin/commit-graph.c: remove subcommand-less usage string
96
40
- Test update.
97
+ Message fix.
98
99
+ Will merge to 'next'.
100
43
-* cb/pcre2-chartables-leakfix (2019-10-18) 3 commits
44
- (merged to 'next' on 2019-10-18 at 5bc67c64fd)
45
- + grep: avoid leak of chartables in PCRE2
46
- + grep: make PCRE2 aware of custom allocator
47
- + grep: make PCRE1 aware of custom allocator
101
49
- Leakfix.
102
+* dl/doc-diff-no-index-implies-exit-code (2019-10-30) 1 commit
103
+ - git-diff.txt: document return code of `--no-index`
104
105
+ Doc update.
106
52
-* dl/submodule-set-branch (2019-10-23) 1 commit
53
- (merged to 'next' on 2019-10-23 at bb485c040f)
54
- + t7419: change test_must_fail to ! for grep
107
+ Will merge to 'next'.
108
56
- Test update.
109
110
+* dl/submodule-set-url (2019-10-30) 1 commit
111
+ - submodule: teach set-url subcommand
112
59
-* ds/feature-macros (2019-10-24) 1 commit
60
- (merged to 'next' on 2019-10-24 at 9c74bfb14c)
61
- + repo-settings: read an int for index.version
113
+ "git submodule" learned a subcommand "set-url".
114
63
- The codepath that reads the index.version configuration was broken
64
- with a recent update, which has been corrected.
115
116
+* js/vreportf-wo-buffering (2019-10-30) 1 commit
117
+ - vreportf(): avoid relying on stdio buffering
118
67
-* js/azure-ci-osx-fix (2019-10-23) 1 commit
68
- (merged to 'next' on 2019-10-23 at c7fcd4f8b6)
69
- + ci(osx): use new location of the `perforce` cask
119
+ Messages from die() etc. can be mixed up from multiple processes
120
+ without even line buffering on Windows, which has been worked
121
+ around.
122
71
- Update installation procedure for Perforce on MacOS in the CI jobs
72
- running on Azure pipelines, which was failing.
123
124
+* ma/bisect-doc-sample-update (2019-10-29) 1 commit
125
+ - Documentation/git-bisect.txt: add --no-ff to merge command
126
75
-* mb/clarify-zsh-completion-doc (2019-10-18) 1 commit
76
- (merged to 'next' on 2019-10-21 at 21a4eb2fe8)
77
- + completion: clarify installation instruction for zsh
127
+ "git merge --no-commit" needs "--no-ff" if you do not want to move
128
+ HEAD, which has been corrected in the manual page for "git bisect".
129
79
- The installation instruction for zsh completion script (in
80
- contrib/) has been a bit improved.
130
+ Will merge to 'next'.
131
132
83
-* nr/diff-highlight-indent-fix (2019-10-15) 1 commit
84
- (merged to 'next' on 2019-10-21 at 8ce6000ec5)
85
- + diff-highlight: fix a whitespace nit
133
+* mr/clone-dir-exists-to-path-exists (2019-10-29) 1 commit
134
+ - clone: rename static function `dir_exists()`.
135
136
Code cleanup.
137
138
+ Will merge to 'next'.
139
90
-* sb/userdiff-dts (2019-10-21) 1 commit
91
- (merged to 'next' on 2019-10-21 at eafa01fb62)
92
- + userdiff: fix some corner cases in dts regex
140
94
- Tweak userdiff patterns for dts.
95
- As adding finishing touches to the new feature in the upcoming
96
- release, this is fast-tracked.
141
+* pb/help-list-gitsubmodules-among-guides (2019-10-29) 1 commit
142
+ - help: add gitsubmodules to the list of guides
143
144
+ Help update.
145
99
-* sg/ci-osx-gcc8-fix (2019-10-24) 1 commit
100
- (merged to 'next' on 2019-10-24 at 58039e24ec)
101
- + ci: fix GCC install in the Travis CI GCC OSX job
146
+ Will merge to 'next'.
147
103
- CI build fix.
148
149
+* pb/no-recursive-reset-hard-in-worktree-add (2019-10-30) 1 commit
150
+ - worktree: teach "add" to ignore submodule.recurse config
151
106
-* sg/progress-fix (2019-10-21) 1 commit
107
- (merged to 'next' on 2019-10-21 at 678e344b22)
108
- + test-progress: fix test failures on big-endian systems
152
+ "git worktree add" internally calls "reset --hard" that should not
153
+ descend into submodules, even when submodule.recurse configuration
154
+ is set, but it was affected. This has been correct.
155
+
156
+ Will merge to 'next'.
157
110
- Byte-order fix the recent update to progress display code.
111
- The breakage being fixed is a regression since the last relesae.
158
159
+* sg/blame-indent-heuristics-is-now-the-default (2019-10-29) 1 commit
160
+ - builtin/blame.c: remove '--indent-heuristic' from usage string
161
114
-* wb/fsmonitor-bitmap-fix (2019-10-12) 1 commit
115
- (merged to 'next' on 2019-10-15 at 1cc4091346)
116
- + fsmonitor: don't fill bitmap with entries to be removed
162
+ Message update.
163
118
- A segfault fix.
164
+ Will merge to 'next'.
165
166
--------------------------------------------------
121
-[New Topics]
167
+[Stalled]
168
+
169
+* ra/rebase-i-more-options (2019-09-09) 6 commits
170
+ - rebase: add --reset-author-date
171
+ - rebase -i: support --ignore-date
172
+ - sequencer: rename amend_author to author_to_rename
173
+ - rebase -i: support --committer-date-is-author-date
174
+ - sequencer: allow callers of read_author_script() to ignore fields
175
+ - rebase -i: add --ignore-whitespace flag
176
+
177
+ "git rebase -i" learned a few options that are known by "git
178
+ rebase" proper.
179
+
180
+ Needs to consider existing GIT_COMMITTER_DATE environment, etc.
181
+ cf. <5adde732-173b-d24d-d23f-bb4d043076d7@gmail.com>
182
+
183
+
184
+* vn/reset-deleted-ita (2019-07-26) 1 commit
185
+ - reset: unstage empty deleted ita files
186
+
187
+ "git reset HEAD [<pathspec>]" did not reset an empty file that was
188
+ added with the intent-to-add bit.
189
+
190
+ Expecting a reroll.
191
+
192
+
193
+* jn/unknown-index-extensions (2018-11-21) 2 commits
194
+ - index: offer advice for unknown index extensions
195
+ - index: do not warn about unrecognized extensions
196
+
197
+ A bit too alarming warning given when unknown index extensions
198
+ exist is getting revamped.
199
+
200
+ Expecting a reroll.
201
+
202
+
203
+* jc/format-patch-delay-message-id (2019-04-05) 1 commit
204
+ - format-patch: move message-id and related headers to the end
205
+
206
+ The location "git format-patch --thread" adds the Message-Id:
207
+ header in the series of header fields has been moved down, which
208
+ may help working around a suspected bug in GMail MSA, reported at
209
+ <CAHk-=whP1stFZNAaJiMi5eZ9rj0MRt20Y_yHVczZPH+O01d+sA@mail.gmail.com>
210
+
211
+ Waiting for feedback to see if it truly helps.
212
+ Needs tests.
213
+
214
+
215
+* js/protocol-advertise-multi (2018-12-28) 1 commit
216
+ - protocol: advertise multiple supported versions
217
+
218
+ The transport layer has been updated so that the protocol version
219
+ used can be negotiated between the parties, by the initiator
220
+ listing the protocol versions it is willing to talk, and the other
221
+ side choosing from one of them.
222
+
223
+ Expecting a reroll.
224
+ cf. <CANq=j3u-zdb_FvNJGPCmygNMScseav63GhVvBX3NcVS4f7TejA@mail.gmail.com>
225
+
226
+
227
+* mk/use-size-t-in-zlib (2018-10-15) 1 commit
228
+ - zlib.c: use size_t for size
229
+
230
+ The wrapper to call into zlib followed our long tradition to use
231
+ "unsigned long" for sizes of regions in memory, which have been
232
+ updated to use "size_t".
233
+
234
+--------------------------------------------------
235
+[Cooking]
236
237
* hv/bitshift-constants-in-blame (2019-10-21) 1 commit
238
(merged to 'next' on 2019-10-24 at bc84aae4d4)
@@ -130,35 +244,38 @@ of the repositories listed at
244
Will cook in 'next'.
245
246
133
-* jk/cleanup-object-parsing-and-fsck (2019-10-21) 23 commits
134
- - fsck: accept an oid instead of a "struct tree" for fsck_tree()
135
- - fsck: accept an oid instead of a "struct commit" for fsck_commit()
136
- - fsck: accept an oid instead of a "struct tag" for fsck_tag()
137
- - fsck: rename vague "oid" local variables
138
- - fsck: don't require an object struct in verify_headers()
139
- - fsck: don't require an object struct for fsck_ident()
140
- - fsck: drop blob struct from fsck_finish()
141
- - fsck: accept an oid instead of a "struct blob" for fsck_blob()
142
- - fsck: don't require an object struct for report()
143
- - fsck: only require an oid for skiplist functions
144
- - fsck: only provide oid/type in fsck_error callback
145
- - fsck: don't require object structs for display functions
146
- - fsck: use oids rather than objects for object_name API
147
- - fsck_describe_object(): build on our get_object_name() primitive
148
- - fsck: unify object-name code
149
- - fsck: require an actual buffer for non-blobs
150
- - fsck: stop checking tag->tagged
151
- - fsck: stop checking commit->parent counts
152
- - fsck: stop checking commit->tree value
153
- - remember commit/tag parse failures
154
- - parse_tag_buffer(): treat NULL tag pointer as parse error
155
- - parse_commit_buffer(): treat lookup_tree() failure as parse error
156
- - parse_commit_buffer(): treat lookup_commit() failure as parse error
247
+* jk/cleanup-object-parsing-and-fsck (2019-10-28) 23 commits
248
+ (merged to 'next' on 2019-10-30 at 6e8b84557e)
249
+ + fsck: accept an oid instead of a "struct tree" for fsck_tree()
250
+ + fsck: accept an oid instead of a "struct commit" for fsck_commit()
251
+ + fsck: accept an oid instead of a "struct tag" for fsck_tag()
252
+ + fsck: rename vague "oid" local variables
253
+ + fsck: don't require an object struct in verify_headers()
254
+ + fsck: don't require an object struct for fsck_ident()
255
+ + fsck: drop blob struct from fsck_finish()
256
+ + fsck: accept an oid instead of a "struct blob" for fsck_blob()
257
+ + fsck: don't require an object struct for report()
258
+ + fsck: only require an oid for skiplist functions
259
+ + fsck: only provide oid/type in fsck_error callback
260
+ + fsck: don't require object structs for display functions
261
+ + fsck: use oids rather than objects for object_name API
262
+ + fsck_describe_object(): build on our get_object_name() primitive
263
+ + fsck: unify object-name code
264
+ + fsck: require an actual buffer for non-blobs
265
+ + fsck: stop checking tag->tagged
266
+ + fsck: stop checking commit->parent counts
267
+ + fsck: stop checking commit->tree value
268
+ + commit, tag: don't set parsed bit for parse failures
269
+ + parse_tag_buffer(): treat NULL tag pointer as parse error
270
+ + parse_commit_buffer(): treat lookup_tree() failure as parse error
271
+ + parse_commit_buffer(): treat lookup_commit() failure as parse error
272
273
Crufty code and logic accumulated over time around the object
274
parsing and low-level object access used in "git fsck" have been
275
cleaned up.
276
277
+ Will cook in 'next'.
278
+
279
280
* js/rebase-deprecate-preserve-merges (2019-10-21) 1 commit
281
(merged to 'next' on 2019-10-24 at 82fa49bbf2)
@@ -178,14 +295,14 @@ of the repositories listed at
295
Expecting a reroll.
296
297
181
-* ds/commit-graph-on-fetch (2019-10-24) 2 commits
182
- - commit-graph: fix writing first commit-graph during fetch
183
- - t5510-fetch.sh: demonstrate fetch.writeCommitGraph bug
298
+* ds/commit-graph-on-fetch (2019-10-25) 2 commits
299
+ (merged to 'next' on 2019-10-30 at 3ca711f743)
300
+ + commit-graph: fix writing first commit-graph during fetch
301
+ + t5510-fetch.sh: demonstrate fetch.writeCommitGraph bug
302
303
"git commit-grph write" hit BUG() in corner cases.
304
187
- Expecting a final fix-up.
188
- cf. <a9ba6007-aeb9-96b4-9436-8e956798be59@gmail.com> <20191023150402.GB26017@szeder.dev>
305
+ Will cook in 'next'.
306
307
308
* jc/am-show-current-patch-docfix (2019-10-23) 1 commit
@@ -208,6 +325,7 @@ of the repositories listed at
325
cherry-pick better.
326
327
Will cook in 'next'.
328
+ cf. <9d550cd9-08a2-eee5-7d7f-63678285accc@gmail.com>
329
330
331
* sg/dir-trie-fixes (2019-10-23) 5 commits
@@ -247,7 +365,7 @@ of the repositories listed at
365
+ t4108: remove git command upstream of pipe
366
+ t4108: replace create_file with test_write_lines
367
250
- "git apply --3way" learned to honor merge.conflictsStyle
368
+ "git apply --3way" learned to honor merge.conflictStyle
369
configuration variable, like merges would.
370
371
Will cook in 'next'.
@@ -263,80 +381,13 @@ of the repositories listed at
381
382
383
* jt/delay-fetch-if-missing (2019-10-24) 1 commit
266
- - fetch: delay fetch_if_missing=0 until after config
384
+ (merged to 'next' on 2019-10-30 at 6c884f3267)
385
+ + fetch: delay fetch_if_missing=0 until after config
386
387
Work-around a lazy fetch glitch.
388
270
---------------------------------------------------
271
-[Stalled]
272
-
273
-* ra/rebase-i-more-options (2019-09-09) 6 commits
274
- - rebase: add --reset-author-date
275
- - rebase -i: support --ignore-date
276
- - sequencer: rename amend_author to author_to_rename
277
- - rebase -i: support --committer-date-is-author-date
278
- - sequencer: allow callers of read_author_script() to ignore fields
279
- - rebase -i: add --ignore-whitespace flag
280
-
281
- "git rebase -i" learned a few options that are known by "git
282
- rebase" proper.
283
-
284
- Needs to consider existing GIT_COMMITTER_DATE environment, etc.
285
- cf. <5adde732-173b-d24d-d23f-bb4d043076d7@gmail.com>
286
-
287
-
288
-* vn/reset-deleted-ita (2019-07-26) 1 commit
289
- - reset: unstage empty deleted ita files
290
-
291
- "git reset HEAD [<pathspec>]" did not reset an empty file that was
292
- added with the intent-to-add bit.
293
-
294
- Expecting a reroll.
295
-
296
-
297
-* jn/unknown-index-extensions (2018-11-21) 2 commits
298
- - index: offer advice for unknown index extensions
299
- - index: do not warn about unrecognized extensions
300
-
301
- A bit too alarming warning given when unknown index extensions
302
- exist is getting revamped.
303
-
304
- Expecting a reroll.
305
-
306
-
307
-* jc/format-patch-delay-message-id (2019-04-05) 1 commit
308
- - format-patch: move message-id and related headers to the end
309
-
310
- The location "git format-patch --thread" adds the Message-Id:
311
- header in the series of header fields has been moved down, which
312
- may help working around a suspected bug in GMail MSA, reported at
313
- <CAHk-=whP1stFZNAaJiMi5eZ9rj0MRt20Y_yHVczZPH+O01d+sA@mail.gmail.com>
314
-
315
- Waiting for feedback to see if it truly helps.
316
- Needs tests.
317
-
318
-
319
-* js/protocol-advertise-multi (2018-12-28) 1 commit
320
- - protocol: advertise multiple supported versions
321
-
322
- The transport layer has been updated so that the protocol version
323
- used can be negotiated between the parties, by the initiator
324
- listing the protocol versions it is willing to talk, and the other
325
- side choosing from one of them.
326
-
327
- Expecting a reroll.
328
- cf. <CANq=j3u-zdb_FvNJGPCmygNMScseav63GhVvBX3NcVS4f7TejA@mail.gmail.com>
329
-
330
-
331
-* mk/use-size-t-in-zlib (2018-10-15) 1 commit
332
- - zlib.c: use size_t for size
389
+ Will cook in 'next'.
390
334
- The wrapper to call into zlib followed our long tradition to use
335
- "unsigned long" for sizes of regions in memory, which have been
336
- updated to use "size_t".
337
-
338
---------------------------------------------------
339
-[Cooking]
391
392
* dd/notes-copy-default-dst-to-head (2019-10-18) 2 commits
393
(merged to 'next' on 2019-10-18 at 2588a175ec)
@@ -372,15 +423,14 @@ of the repositories listed at
423
Will cook in 'next'.
424
425
375
-* js/git-path-head-dot-lock-fix (2019-10-24) 2 commits
376
- (merged to 'next' on 2019-10-24 at 3a7533c171)
377
- + git_path(): handle `.lock` files correctly
378
- + t1400: wrap setup code in test case
426
+* js/git-path-head-dot-lock-fix (2019-10-29) 2 commits
427
+ - git_path(): handle `.lock` files correctly
428
+ - t1400: wrap setup code in test case
429
430
"git rev-parse --git-path HEAD.lock" did not give the right path
431
when run in a secondary worktree.
432
383
- Will cook in 'next'.
433
+ Will merge to 'next'.
434
435
436
* pw/post-commit-from-sequencer (2019-10-16) 6 commits
@@ -471,30 +521,32 @@ of the repositories listed at
521
Will cook in 'next'.
522
523
474
-* bc/hash-independent-tests-part-6 (2019-10-06) 15 commits
475
- - t4048: abstract away SHA-1-specific constants
476
- - t4045: make hash-size independent
477
- - t4044: update test to work with SHA-256
478
- - t4039: abstract away SHA-1-specific constants
479
- - t4038: abstract away SHA-1 specific constants
480
- - t4034: abstract away SHA-1-specific constants
481
- - t4027: make hash-size independent
482
- - t4015: abstract away SHA-1-specific constants
483
- - t4011: abstract away SHA-1-specific constants
484
- - t4010: abstract away SHA-1-specific constants
485
- - t3429: remove SHA1 annotation
486
- - t1305: avoid comparing extensions
487
- - rev-parse: add an --object-format option
488
- - t/oid-info: add empty tree and empty blob values
489
- - t/oid-info: allow looking up hash algorithm name
524
+* bc/hash-independent-tests-part-6 (2019-10-28) 15 commits
525
+ (merged to 'next' on 2019-10-30 at 70037a3839)
526
+ + t4048: abstract away SHA-1-specific constants
527
+ + t4045: make hash-size independent
528
+ + t4044: update test to work with SHA-256
529
+ + t4039: abstract away SHA-1-specific constants
530
+ + t4038: abstract away SHA-1 specific constants
531
+ + t4034: abstract away SHA-1-specific constants
532
+ + t4027: make hash-size independent
533
+ + t4015: abstract away SHA-1-specific constants
534
+ + t4011: abstract away SHA-1-specific constants
535
+ + t4010: abstract away SHA-1-specific constants
536
+ + t3429: remove SHA1 annotation
537
+ + t1305: avoid comparing extensions
538
+ + rev-parse: add a --show-object-format option
539
+ + t/oid-info: add empty tree and empty blob values
540
+ + t/oid-info: allow looking up hash algorithm name
541
542
Test updates to prepare for SHA-2 transition continues.
543
493
- May be rerolled.
494
- cf. <20191008194012.4s35pbwbh25rblhb@camp.crustytoothpaste.net>
544
+ Will cook in 'next'.
545
546
497
-* ag/sequencer-todo-updates (2019-10-08) 5 commits
547
+* ag/sequencer-todo-updates (2019-10-28) 6 commits
548
+ (merged to 'next' on 2019-10-28 at 85f694d9d3)
549
+ + SQUASH??? tentative leakfix
550
(merged to 'next' on 2019-10-18 at 8dac803e49)
551
+ sequencer: directly call pick_commits() from complete_action()
552
+ rebase: fill `squash_onto' in get_replay_opts()
@@ -506,7 +558,6 @@ of the repositories listed at
558
during sequener operation.
559
560
Will cook in 'next'.
509
- No need for rush, as this does not fix anything nor adds any new feature.
561
562
563
* mt/threaded-grep-in-object-store (2019-10-02) 11 commits