What's cooking (2019/05 #05)
Junio C Hamano committed
May 30, 2019 at 11:27 UTC
09e9214d42b5b0a084d1b78f59cd605d0d0ed5b4
1 file changed
+255
-219
whats-cooking.txt
+255
-219
@@ -1,10 +1,10 @@
1
To: git@vger.kernel.org
2
Bcc: lwn@lwn.net
3
-Subject: What's cooking in git.git (May 2019, #04; Tue, 28)
4
-X-master-at: aa25c82427ae70aebf3b8f970f2afd54e9a2a8c6
5
-X-next-at: 3120a1824446a317099b597aac098c4ec420be6e
3
+Subject: What's cooking in git.git (May 2019, #05; Thu, 30)
4
+X-master-at: 874dd410cecbc2953f624ab6ab9fda10d1650870
5
+X-next-at: f4fbbf30c2866bb423731899b666bc3184d8e162
6
7
-What's cooking in git.git (May 2019, #04; Tue, 28)
7
+What's cooking in git.git (May 2019, #05; Thu, 30)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking. Commits prefixed with
@@ -12,21 +12,194 @@ 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
-Quite a few new topics, most of which are fixes with different
16
-urgency, have been picked up. Perhaps we'd need an extra -rc for
17
-this cycle to squash existing regression at the tip of 'master'.
18
-At this point, the criteria for merging to 'master' is *NOT* "This
19
-is an obviously correct fix", but is "This is an obviously correct
20
-fix for a breakage we introduced during this cycle".
15
+The second round of release candidate has been tagged, after
16
+slipping for several days to merge a handful of last-minute
17
+regression fixes.
18
19
You can find the changes described here in the integration branches
20
of the repositories listed at
21
22
http://git-blame.blogspot.com/p/git-public-repositories.html
23
24
+--------------------------------------------------
25
+[Graduated to "master"]
26
+
27
+* es/doc-gitsubmodules-markup (2019-05-28) 1 commit
28
+ (merged to 'next' on 2019-05-29 at 695bb51514)
29
+ + gitsubmodules: align html and nroff lists
30
+
31
+ Doc markup fix.
32
+
33
+
34
+* ja/diff-opt-typofix (2019-05-19) 1 commit
35
+ (merged to 'next' on 2019-05-19 at fedb594191)
36
+ + diff: fix mistake in translatable strings
37
+
38
+ Typofix.
39
+
40
+
41
+* jh/trace2 (2019-05-28) 1 commit
42
+ (merged to 'next' on 2019-05-29 at 849c4916ac)
43
+ + trace2: fix tracing when NO_PTHREADS is defined
44
+
45
+ Will merge to 'master'.
46
+
47
+
48
+* js/rebase-config-bitfix (2019-05-28) 1 commit
49
+ (merged to 'next' on 2019-05-29 at 77de6e31b6)
50
+ + rebase: replace incorrect logical negation by correct bitwise one
51
+
52
+ Will merge to 'master'.
53
+
54
+
55
+* js/rebase-deprecate-preserve-merges (2019-05-28) 3 commits
56
+ (merged to 'next' on 2019-05-29 at d153fc0d44)
57
+ + rebase docs: recommend `-r` over `-p`
58
+ + docs: say that `--rebase=preserve` is deprecated
59
+ + tests: mark a couple more test cases as requiring `rebase -p`
60
+
61
+ A bit more leftover clean-up to deprepcate "rebase -p".
62
+
63
+
64
+* jt/clone-server-option (2019-05-28) 1 commit
65
+ (merged to 'next' on 2019-05-29 at 30eb487077)
66
+ + fetch-pack: send server options after command
67
+
68
+ A brown-paper-bag bugfix to a change already in 'master'.
69
+
70
+
71
+* nd/diff-parseopt (2019-05-29) 3 commits
72
+ (merged to 'next' on 2019-05-29 at f9eedc21e3)
73
+ + parse-options: check empty value in OPT_INTEGER and OPT_ABBREV
74
+ + diff-parseopt: restore -U (no argument) behavior
75
+ + diff-parseopt: correct variable types that are used by parseopt
76
+
77
+ A brown-paper-bag bugfix to a change already in 'master'.
78
+
79
+ Reducing the noise of the bottom-most patch may be desirable, although
80
+ the change itself is not wrong per-se.
81
+
82
+
83
+* sg/progress-off-by-one-fix (2019-05-28) 1 commit
84
+ (merged to 'next' on 2019-05-29 at 13ea8cc5a5)
85
+ + progress: avoid empty line when breaking the progress line
86
+
87
+ A brown-paper-bag bugfix to a change already in 'master'.
88
+
89
+
90
+* sg/trace2-rename (2019-05-28) 2 commits
91
+ (merged to 'next' on 2019-05-29 at ae7aa4b417)
92
+ + trace2: document the supported values of GIT_TRACE2* env variables
93
+ + trace2: rename environment variables to GIT_TRACE2*
94
+
95
+ Rename environment variables that are used to control the "trace2"
96
+ mechanism to a more readable name.
97
+
98
--------------------------------------------------
99
[New Topics]
100
101
+* po/doc-branch (2019-05-29) 1 commit
102
+ - doc branch: provide examples for listing remote tracking branches
103
+
104
+ RFC
105
+
106
+
107
+* bb/unicode-12.1-reiwa (2019-05-29) 1 commit
108
+ (merged to 'next' on 2019-05-30 at 016465335c)
109
+ + unicode: update the width tables to Unicode 12.1
110
+<<
111
+* bb/unicode-12.1-reiwa (2019-05-29) 1 commit
112
+ - unicode: update the width tables to Unicode 12.1
113
+>>
114
+
115
+ Update to Unicode 12.1 width table.
116
+
117
+ Will cook in 'next'.
118
+
119
+--------------------------------------------------
120
+[Stalled]
121
+
122
+* jn/unknown-index-extensions (2018-11-21) 2 commits
123
+ - index: offer advice for unknown index extensions
124
+ - index: do not warn about unrecognized extensions
125
+
126
+ A bit too alarming warning given when unknown index extensions
127
+ exist is getting revamped.
128
+
129
+ Expecting a reroll.
130
+
131
+
132
+* jc/format-patch-delay-message-id (2019-04-05) 1 commit
133
+ - format-patch: move message-id and related headers to the end
134
+
135
+ The location "git format-patch --thread" adds the Message-Id:
136
+ header in the series of header fields has been moved down, which
137
+ may help working around a suspected bug in GMail MSA, reported at
138
+ <CAHk-=whP1stFZNAaJiMi5eZ9rj0MRt20Y_yHVczZPH+O01d+sA@mail.gmail.com>
139
+
140
+ Waiting for feedback to see if it truly helps.
141
+ Needs tests.
142
+
143
+
144
+* jt/fetch-cdn-offload (2019-03-12) 9 commits
145
+ - SQUASH???
146
+ - upload-pack: send part of packfile response as uri
147
+ - fetch-pack: support more than one pack lockfile
148
+ - upload-pack: refactor reading of pack-objects out
149
+ - Documentation: add Packfile URIs design doc
150
+ - Documentation: order protocol v2 sections
151
+ - http-fetch: support fetching packfiles by URL
152
+ - http: improve documentation of http_pack_request
153
+ - http: use --stdin when getting dumb HTTP pack
154
+
155
+ WIP for allowing a response to "git fetch" to instruct the bulk of
156
+ the pack contents to be instead taken from elsewhere (aka CDN).
157
+
158
+ Stalled
159
+
160
+
161
+* js/add-i-coalesce-after-editing-hunk (2018-08-28) 1 commit
162
+ - add -p: coalesce hunks before testing applicability
163
+
164
+ Applicability check after a patch is edited in a "git add -i/p"
165
+ session has been improved.
166
+
167
+ Will drop as "add -i in C" topic seems to be getting ready to test.
168
+
169
+
170
+* js/protocol-advertise-multi (2018-12-28) 1 commit
171
+ - protocol: advertise multiple supported versions
172
+
173
+ The transport layer has been updated so that the protocol version
174
+ used can be negotiated between the parties, by the initiator
175
+ listing the protocol versions it is willing to talk, and the other
176
+ side choosing from one of them.
177
+
178
+ Expecting a reroll.
179
+ cf. <CANq=j3u-zdb_FvNJGPCmygNMScseav63GhVvBX3NcVS4f7TejA@mail.gmail.com>
180
+
181
+
182
+* mk/use-size-t-in-zlib (2018-10-15) 1 commit
183
+ - zlib.c: use size_t for size
184
+
185
+ The wrapper to call into zlib followed our long tradition to use
186
+ "unsigned long" for sizes of regions in memory, which have been
187
+ updated to use "size_t".
188
+
189
+
190
+* dl/remote-save-to-push (2018-12-11) 1 commit
191
+ - remote: add --save-to-push option to git remote set-url
192
+
193
+ "git remote set-url" learned a new option that moves existing value
194
+ of the URL field to pushURL field of the remote before replacing
195
+ the URL field with a new value.
196
+
197
+ Anybody who wants to champion this topic?
198
+ I am personally not yet quite convinced if this is worth pursuing.
199
+
200
+--------------------------------------------------
201
+[Cooking]
202
+
203
* ab/hash-object-doc (2019-05-28) 1 commit
204
- hash-object doc: stop mentioning git-cvsimport
205
@@ -35,146 +208,118 @@ of the repositories listed at
208
Will merge to 'next'.
209
210
38
-* cc/list-objects-filter-wo-sparse-path (2019-05-28) 2 commits
39
- - SQUASH???
40
- - list-objects-filter: disable 'sparse:path' filters
211
+* cc/list-objects-filter-wo-sparse-path (2019-05-29) 1 commit
212
+ (merged to 'next' on 2019-05-30 at 5a294203ad)
213
+ + list-objects-filter: disable 'sparse:path' filters
214
215
Disable "--filter=sparse:path=<path>" that would allow reading from
216
paths on the filesystem.
217
45
- Will merge to 'next'.
218
+ Will cook in 'next'.
219
220
221
* ds/object-info-for-prefetch-fix (2019-05-28) 1 commit
49
- - sha1-file: split OBJECT_INFO_FOR_PREFETCH
222
+ (merged to 'next' on 2019-05-29 at ee0055b276)
223
+ + sha1-file: split OBJECT_INFO_FOR_PREFETCH
224
51
- Code cleanup.
225
+ Code cleanup and futureproof.
226
53
- Will merge to 'next'.
227
+ Will cook in 'next'.
228
229
230
* ds/topo-traversal-using-commit-graph (2019-05-28) 2 commits
57
- - revision: keep topo-walk free of unintersting commits
58
- - revision: use generation for A..B --topo-order queries
231
+ (merged to 'next' on 2019-05-30 at 590527995e)
232
+ + revision: keep topo-walk free of unintersting commits
233
+ + revision: use generation for A..B --topo-order queries
234
235
Prepare use of reachability index in topological walker that works
236
on a range (A..B).
237
63
- Will merge to 'next'.
64
-
65
-
66
-* es/doc-gitsubmodules-markup (2019-05-28) 1 commit
67
- - gitsubmodules: align html and nroff lists
68
-
69
- Doc markup fix.
70
-
71
- Will merge to 'next'.
238
+ Will cook in 'next'.
239
240
241
* es/git-debugger-doc (2019-05-28) 1 commit
75
- - doc: hint about GIT_DEBUGGER in CodingGuidelines
242
+ (merged to 'next' on 2019-05-29 at 449ba4ae6c)
243
+ + doc: hint about GIT_DEBUGGER in CodingGuidelines
244
245
Doc update.
246
79
- Will merge to 'next'.
247
+ Will cook in 'next'.
248
249
250
* es/grep-require-name-when-needed (2019-05-28) 1 commit
83
- - grep: fail if call could output and name is null
251
+ (merged to 'next' on 2019-05-29 at e1ec57894a)
252
+ + grep: fail if call could output and name is null
253
254
More parameter validation.
255
87
- Will merge to 'next'.
256
+ Will cook in 'next'.
257
258
259
* ew/server-info-remove-crufts (2019-05-28) 1 commit
91
- - server-info: do not list unlinked packs
260
+ (merged to 'next' on 2019-05-29 at 655ba18f30)
261
+ + server-info: do not list unlinked packs
262
263
"git update-server-info" used to leave stale packfiles in its
264
output, which has been corrected.
265
96
- Will merge to 'next'.
97
-
98
-
99
-* jh/trace2 (2019-05-28) 1 commit
100
- - trace2: fix tracing when NO_PTHREADS is defined
101
-
102
- Will merge to 'next' and then to 'master'.
266
+ Will cook in 'next'.
267
268
269
* jk/HEAD-symref-in-xfer-namespaces (2019-05-28) 1 commit
106
- - upload-pack: strip namespace from symref data
270
+ (merged to 'next' on 2019-05-29 at c2cfe38955)
271
+ + upload-pack: strip namespace from symref data
272
273
The server side support for "git fetch" used to show incorrect
274
value for the HEAD symbolic ref when the namespace feature is in
275
use, which has been corrected.
276
112
- Will merge to 'next'.
277
+ Will cook in 'next'.
278
279
280
* jk/am-i-resolved-fix (2019-05-28) 4 commits
116
- - am: fix --interactive HEAD tree resolution
117
- - am: drop tty requirement for --interactive
118
- - am: read interactive input from stdin
119
- - am: simplify prompt response handling
281
+ (merged to 'next' on 2019-05-29 at e711103b1a)
282
+ + am: fix --interactive HEAD tree resolution
283
+ + am: drop tty requirement for --interactive
284
+ + am: read interactive input from stdin
285
+ + am: simplify prompt response handling
286
287
"git am -i --resolved" segfaulted after trying to see a commit as
288
if it were a tree, which has been corrected.
289
124
- Will merge to 'next'.
290
+ Will cook in 'next'.
291
292
293
* js/bisect-helper-check-get-oid-return-value (2019-05-28) 1 commit
128
- - bisect--helper: verify HEAD could be parsed before continuing
294
+ (merged to 'next' on 2019-05-29 at 24125b3bc0)
295
+ + bisect--helper: verify HEAD could be parsed before continuing
296
297
Code cleanup.
298
132
- Will merge to 'next'.
299
+ Will cook in 'next'.
300
301
302
* js/bundle-verify-require-object-store (2019-05-28) 1 commit
136
- - bundle verify: error out if called without an object database
303
+ (merged to 'next' on 2019-05-29 at 747fbbaf11)
304
+ + bundle verify: error out if called without an object database
305
306
"git bundle verify" needs to see if prerequisite objects exist in
307
the receiving repository, but the command did not check if we are
308
in a repository upfront, which has been corrected.
309
142
- Will merge to 'next'.
310
+ Will cook in 'next'.
311
312
313
* js/fsmonitor-unflake (2019-05-28) 2 commits
146
- - mark_fsmonitor_valid(): mark the index as changed if needed
147
- - fill_stat_cache_info(): prepare for an fsmonitor fix
314
+ (merged to 'next' on 2019-05-30 at 1aa850bc59)
315
+ + mark_fsmonitor_valid(): mark the index as changed if needed
316
+ + fill_stat_cache_info(): prepare for an fsmonitor fix
317
318
The data collected by fsmonitor was not properly written back to
319
the on-disk index file, breaking t7519 tests occasionally, which
320
has been corrected.
321
153
- Will merge to 'next'.
154
-
155
-
156
-* js/rebase-config-bitfix (2019-05-28) 1 commit
157
- - rebase: replace incorrect logical negation by correct bitwise one
158
-
159
- Will merge to 'next'.
160
-
161
-
162
-* js/rebase-deprecate-preserve-merges (2019-05-28) 3 commits
163
- - rebase docs: recommend `-r` over `-p`
164
- - docs: say that `--rebase=preserve` is deprecated
165
- - tests: mark a couple more test cases as requiring `rebase -p`
166
-
167
- A bit more leftover clean-up to deprepcate "rebase -p".
168
-
169
- Will merge to 'next' and then to 'master'.
170
-
171
-
172
-* jt/clone-server-option (2019-05-28) 1 commit
173
- - fetch-pack: send server options after command
174
-
175
- A brown-paper-bag bugfix to a change already in 'master'.
176
-
177
- Will merge to 'next' and then to 'master'.
322
+ Will cook in 'next'.
323
324
325
* mm/p4-unshelve-windows-fix (2019-05-28) 1 commit
@@ -187,19 +332,6 @@ of the repositories listed at
332
Will merge to 'next'.
333
334
190
-* nd/diff-parseopt (2019-05-28) 3 commits
191
- - parse-options: check empty value in OPT_INTEGER and OPT_ABBREV
192
- - diff-parseopt: restore -U (no argument) behavior
193
- - diff-parseopt: correct variable types that are used by parseopt
194
-
195
- A brown-paper-bag bugfix to a change already in 'master'.
196
-
197
- Will merge to 'next' and then to 'master'.
198
-
199
- Reducing the noise of the bottom-most patch may be desirable, although
200
- the change itself is not wrong per-se.
201
-
202
-
335
* pb/request-pull-verify-remote-ref (2019-05-28) 2 commits
336
- request-pull: warn if the remote object is not the same as the local one
337
- request-pull: quote regex metacharacters in local ref
@@ -221,43 +353,28 @@ of the repositories listed at
353
Will merge to 'next'.
354
355
224
-* sg/progress-off-by-one-fix (2019-05-28) 1 commit
225
- - progress: avoid empty line when breaking the progress line
226
-
227
- A brown-paper-bag bugfix to a change already in 'master'.
228
-
229
- Will merge to 'next' and then to 'master'.
230
-
231
-
232
-
233
-* sg/trace2-rename (2019-05-28) 2 commits
234
- - trace2: document the supported values of GIT_TRACE2* env variables
235
- - trace2: rename environment variables to GIT_TRACE2*
236
-
237
- Rename environment variables that are used to control the "trace2"
238
- mechanism to a more readable name.
239
-
240
- Will merge to 'next' and then to 'master'.
241
-
242
-
356
* sw/git-p4-unshelve-branched-files (2019-05-28) 1 commit
244
- - git-p4: allow unshelving of branched files
357
+ (merged to 'next' on 2019-05-30 at e1985f61fc)
358
+ + git-p4: allow unshelving of branched files
359
360
"git p4" update.
361
248
- Will merge to 'next'.
362
+ Will cook in 'next'.
363
364
365
* vv/merge-squash-with-explicit-commit (2019-05-28) 1 commit
252
- - merge: refuse --commit with --squash
366
+ (merged to 'next' on 2019-05-29 at 209baa3e55)
367
+ + merge: refuse --commit with --squash
368
369
"git merge --squash" is designed to update the working tree and the
370
index without creating the commit, and this cannot be countermanded
371
by adding the "--commit" option; the command now refuses to work
372
when both options are given.
373
374
+ Will cook in 'next'.
375
+
376
260
-* xl/record-partial-clone-origin (2019-05-28) 1 commit
377
+* xl/record-partial-clone-origin (2019-05-29) 1 commit
378
- clone: respect user supplied origin name when setting up partial clone
379
380
When creating a partial clone, the object filtering criteria is
@@ -267,89 +384,6 @@ of the repositories listed at
384
385
Will merge to 'next'.
386
270
---------------------------------------------------
271
-[Stalled]
272
-
273
-* jn/unknown-index-extensions (2018-11-21) 2 commits
274
- - index: offer advice for unknown index extensions
275
- - index: do not warn about unrecognized extensions
276
-
277
- A bit too alarming warning given when unknown index extensions
278
- exist is getting revamped.
279
-
280
- Expecting a reroll.
281
-
282
-
283
-* jc/format-patch-delay-message-id (2019-04-05) 1 commit
284
- - format-patch: move message-id and related headers to the end
285
-
286
- The location "git format-patch --thread" adds the Message-Id:
287
- header in the series of header fields has been moved down, which
288
- may help working around a suspected bug in GMail MSA, reported at
289
- <CAHk-=whP1stFZNAaJiMi5eZ9rj0MRt20Y_yHVczZPH+O01d+sA@mail.gmail.com>
290
-
291
- Waiting for feedback to see if it truly helps.
292
- Needs tests.
293
-
294
-
295
-* jt/fetch-cdn-offload (2019-03-12) 9 commits
296
- - SQUASH???
297
- - upload-pack: send part of packfile response as uri
298
- - fetch-pack: support more than one pack lockfile
299
- - upload-pack: refactor reading of pack-objects out
300
- - Documentation: add Packfile URIs design doc
301
- - Documentation: order protocol v2 sections
302
- - http-fetch: support fetching packfiles by URL
303
- - http: improve documentation of http_pack_request
304
- - http: use --stdin when getting dumb HTTP pack
305
-
306
- WIP for allowing a response to "git fetch" to instruct the bulk of
307
- the pack contents to be instead taken from elsewhere (aka CDN).
308
-
309
- Stalled
310
-
311
-
312
-* js/add-i-coalesce-after-editing-hunk (2018-08-28) 1 commit
313
- - add -p: coalesce hunks before testing applicability
314
-
315
- Applicability check after a patch is edited in a "git add -i/p"
316
- session has been improved.
317
-
318
- Will drop as "add -i in C" topic seems to be getting ready to test.
319
-
320
-
321
-* js/protocol-advertise-multi (2018-12-28) 1 commit
322
- - protocol: advertise multiple supported versions
323
-
324
- The transport layer has been updated so that the protocol version
325
- used can be negotiated between the parties, by the initiator
326
- listing the protocol versions it is willing to talk, and the other
327
- side choosing from one of them.
328
-
329
- Expecting a reroll.
330
- cf. <CANq=j3u-zdb_FvNJGPCmygNMScseav63GhVvBX3NcVS4f7TejA@mail.gmail.com>
331
-
332
-
333
-* mk/use-size-t-in-zlib (2018-10-15) 1 commit
334
- - zlib.c: use size_t for size
335
-
336
- The wrapper to call into zlib followed our long tradition to use
337
- "unsigned long" for sizes of regions in memory, which have been
338
- updated to use "size_t".
339
-
340
-
341
-* dl/remote-save-to-push (2018-12-11) 1 commit
342
- - remote: add --save-to-push option to git remote set-url
343
-
344
- "git remote set-url" learned a new option that moves existing value
345
- of the URL field to pushURL field of the remote before replacing
346
- the URL field with a new value.
347
-
348
- Anybody who wants to champion this topic?
349
- I am personally not yet quite convinced if this is worth pursuing.
350
-
351
---------------------------------------------------
352
-[Cooking]
387
388
* ab/fail-prereqs-in-test (2019-05-14) 1 commit
389
(merged to 'next' on 2019-05-16 at d1be55f485)
@@ -388,15 +422,20 @@ of the repositories listed at
422
423
424
* jt/partial-clone-missing-ref-delta-base (2019-05-15) 2 commits
391
- - index-pack: prefetch missing REF_DELTA bases
392
- - t5616: refactor packfile replacement
425
+ (merged to 'next' on 2019-05-29 at 5d7573a151)
426
+ + index-pack: prefetch missing REF_DELTA bases
427
+ + t5616: refactor packfile replacement
428
429
"git fetch" into a lazy clone forgot to fetch base objects that are
430
necessary to complete delta in a thin packfile, which has been
431
corrected.
432
433
+ Will cook in 'next'.
434
+
435
399
-* bl/userdiff-octave (2019-05-19) 1 commit
436
+* bl/userdiff-octave (2019-05-29) 2 commits
437
+ (merged to 'next' on 2019-05-29 at 6ed07afc89)
438
+ + userdiff: fix grammar and style issues
439
(merged to 'next' on 2019-05-19 at 9ea1180d6c)
440
+ userdiff: add Octave
441
@@ -453,7 +492,8 @@ of the repositories listed at
492
493
494
* ba/clone-remote-submodules (2019-05-28) 1 commit
456
- - clone: add `--remote-submodules` flag
495
+ (merged to 'next' on 2019-05-29 at 71972f94c2)
496
+ + clone: add `--remote-submodules` flag
497
498
"git clone --recurse-submodules" learned to set up the submodules
499
to ignore commit object names recorded in the superproject gitlink
@@ -461,6 +501,8 @@ of the repositories listed at
501
remote-tracking branches from the get-go, by passing the new
502
"--remote-submodules" option.
503
504
+ Will cook in 'next'.
505
+
506
507
* ds/close-object-store (2019-05-28) 3 commits
508
- packfile: rename close_all_packs to close_object_store
@@ -477,16 +519,8 @@ of the repositories listed at
519
Waiting on ds/commit-graph-write-refactor to stabilize.
520
521
480
-* ja/diff-opt-typofix (2019-05-19) 1 commit
481
- (merged to 'next' on 2019-05-19 at fedb594191)
482
- + diff: fix mistake in translatable strings
483
-
484
- Typofix.
485
-
486
- Will merge to 'master'.
487
-
488
-
489
-* ml/userdiff-rust (2019-05-17) 1 commit
522
+* ml/userdiff-rust (2019-05-30) 2 commits
523
+ - userdiff: two simplifications of patterns for rust
524
(merged to 'next' on 2019-05-19 at 1266fddce5)
525
+ userdiff: add built-in pattern for rust
526
@@ -522,11 +556,12 @@ of the repositories listed at
556
Will cook in 'next'.
557
558
525
-* ab/send-email-transferencoding-fix (2019-05-19) 7 commits
526
- - send-email: fix regression in sendemail.identity parsing
527
- - send-email: document --no-[to|cc|bcc]
528
- - send-email: fix broken transferEncoding tests
529
- - send-email: remove cargo-culted multi-patch pattern in tests
559
+* ab/send-email-transferencoding-fix (2019-05-29) 7 commits
560
+ (merged to 'next' on 2019-05-29 at c8a99d18c0)
561
+ + send-email: fix regression in sendemail.identity parsing
562
+ + send-email: document --no-[to|cc|bcc]
563
+ + send-email: fix broken transferEncoding tests
564
+ + send-email: remove cargo-culted multi-patch pattern in tests
565
(merged to 'next' on 2019-05-13 at 38c6a1e7e0)
566
+ send-email: do defaults -> config -> getopt in that order
567
+ send-email: rename the @bcclist variable for consistency
@@ -539,7 +574,7 @@ of the repositories listed at
574
(finally) redoing the order of setting the default, reading the
575
configuration and command line options.
576
542
- Will merge to 'next'.
577
+ Will cook in 'next'.
578
579
580
* dl/format-patch-notes-config (2019-05-17) 2 commits
@@ -648,7 +683,9 @@ of the repositories listed at
683
with '*' in front.
684
685
651
-* es/first-contrib-tutorial (2019-05-19) 2 commits
686
+* es/first-contrib-tutorial (2019-05-29) 3 commits
687
+ (merged to 'next' on 2019-05-30 at 96317960ab)
688
+ + doc: add some nit fixes to MyFirstContribution
689
(merged to 'next' on 2019-05-19 at 9ddfae82bf)
690
+ documentation: add anchors to MyFirstContribution
691
+ documentation: add tutorial for first contribution
@@ -657,7 +694,6 @@ of the repositories listed at
694
developers.
695
696
Will cook in 'next'.
660
- cf. <20190517190359.21676-1-emilyshaffer@google.com> (v6)
697
698
699
* cc/multi-promisor (2019-04-15) 17 commits