What's cooking (2019/11 #01)
Junio C Hamano committed
Nov 4, 2019 at 14:19 UTC
cbfb543e17fd332140001cbd3ce18fb4649ad8f3
1 file changed
+116
-113
whats-cooking.txt
+116
-113
@@ -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, #07; Wed, 30)
4
-X-master-at: f21f8f5d35b09ecdd1a0112f114436fd2eda7df2
5
-X-next-at: 50e10028f102536c1a9ac2647d3aae9cc8a7c5d7
3
+Subject: What's cooking in git.git (Nov 2019, #01; Mon, 4)
4
+X-master-at: da72936f544fec5a335e66432610e4cef4430991
5
+X-next-at: 9d3f5f5b63cc3ed44eec3428f9e8874fb34f9cc0
6
7
-What's cooking in git.git (Oct 2019, #07; Wed, 30)
7
+What's cooking in git.git (Nov 2019, #01; Mon, 4)
8
--------------------------------------------------
9
10
Here are the topics that have been cooking. Commits prefixed with
@@ -12,9 +12,13 @@ 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
-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.
15
+Git 2.24 has been tagged. Hopefully there needs no immediate brown
16
+paper bag fixes needed for the 'master' branch. The next cycle will
17
+start perhaps early next week by first rewinding the 'next' branch,
18
+after the dust settles. Topics marked as "will cook in next" can be
19
+given a fresh start by ejecting them from 'next' and queueing a new
20
+version (please just ask). Topics currently not in 'next' will then
21
+start getting merged down after all that.
22
23
You can find the changes described here in the integration branches
24
of the repositories listed at
@@ -24,30 +28,116 @@ of the repositories listed at
28
--------------------------------------------------
29
[Graduated to "master"]
30
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()`
31
+* bc/doc-use-docbook-5 (2019-11-02) 1 commit
32
+ (merged to 'next' on 2019-11-02 at 68e379d0b0)
33
+ + manpage-bold-literal.xsl: match for namespaced "d:literal" in template
34
31
- Fix for a (rather old) buffer-overrun bug.
35
+ Finishing touches to the recent update to the build procedure for
36
+ the documentation.
37
38
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
39
+* ds/commit-graph-on-fetch (2019-10-25) 2 commits
40
+ (merged to 'next' on 2019-10-30 at 3ca711f743)
41
+ + commit-graph: fix writing first commit-graph during fetch
42
+ + t5510-fetch.sh: demonstrate fetch.writeCommitGraph bug
43
38
- Fix a rather old bug in gitweb---incremental blame output in
39
- javascript actions mode never worked.
44
+ Regression fix.
45
46
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
47
+* jt/delay-fetch-if-missing (2019-10-24) 1 commit
48
+ (merged to 'next' on 2019-10-30 at 6c884f3267)
49
+ + fetch: delay fetch_if_missing=0 until after config
50
46
- Comment update.
51
+ Work-around a lazy fetch glitch.
52
53
--------------------------------------------------
54
[New Topics]
55
56
+* es/myfirstcontrib-updates (2019-11-02) 3 commits
57
+ - myfirstcontrib: hint to find gitgitgadget allower
58
+ - myfirstcontrib: add dependency installation step
59
+ - myfirstcontrib: add 'psuh' to command-list.txt
60
+
61
+ Doc updates.
62
+
63
+ Will merge to 'next'.
64
+
65
+
66
+* rt/fetch-message-fix (2019-11-02) 1 commit
67
+ - fetch.c: fix typo in a warning message
68
+
69
+ A small message update.
70
+
71
+ Will merge to 'next'.
72
+
73
+--------------------------------------------------
74
+[Stalled]
75
+
76
+* vn/reset-deleted-ita (2019-07-26) 1 commit
77
+ - reset: unstage empty deleted ita files
78
+
79
+ "git reset HEAD [<pathspec>]" did not reset an empty file that was
80
+ added with the intent-to-add bit.
81
+
82
+ Expecting a reroll.
83
+
84
+
85
+* jn/unknown-index-extensions (2018-11-21) 2 commits
86
+ - index: offer advice for unknown index extensions
87
+ - index: do not warn about unrecognized extensions
88
+
89
+ A bit too alarming warning given when unknown index extensions
90
+ exist is getting revamped.
91
+
92
+ Expecting a reroll.
93
+
94
+
95
+* jc/format-patch-delay-message-id (2019-04-05) 1 commit
96
+ - format-patch: move message-id and related headers to the end
97
+
98
+ The location "git format-patch --thread" adds the Message-Id:
99
+ header in the series of header fields has been moved down, which
100
+ may help working around a suspected bug in GMail MSA, reported at
101
+ <CAHk-=whP1stFZNAaJiMi5eZ9rj0MRt20Y_yHVczZPH+O01d+sA@mail.gmail.com>
102
+
103
+ Waiting for feedback to see if it truly helps.
104
+ Needs tests.
105
+
106
+
107
+* js/protocol-advertise-multi (2018-12-28) 1 commit
108
+ - protocol: advertise multiple supported versions
109
+
110
+ The transport layer has been updated so that the protocol version
111
+ used can be negotiated between the parties, by the initiator
112
+ listing the protocol versions it is willing to talk, and the other
113
+ side choosing from one of them.
114
+
115
+ Expecting a reroll.
116
+ cf. <CANq=j3u-zdb_FvNJGPCmygNMScseav63GhVvBX3NcVS4f7TejA@mail.gmail.com>
117
+
118
+
119
+* mk/use-size-t-in-zlib (2018-10-15) 1 commit
120
+ - zlib.c: use size_t for size
121
+
122
+ The wrapper to call into zlib followed our long tradition to use
123
+ "unsigned long" for sizes of regions in memory, which have been
124
+ updated to use "size_t".
125
+
126
+--------------------------------------------------
127
+[Cooking]
128
+
129
+* ra/rebase-i-more-options (2019-11-02) 6 commits
130
+ - rebase: add --reset-author-date
131
+ - rebase -i: support --ignore-date
132
+ - sequencer: rename amend_author to author_to_rename
133
+ - rebase -i: support --committer-date-is-author-date
134
+ - sequencer: allow callers of read_author_script() to ignore fields
135
+ - rebase -i: add --ignore-whitespace flag
136
+
137
+ "git rebase -i" learned a few options that are known by "git
138
+ rebase" proper.
139
+
140
+
141
* en/doc-typofix (2019-10-25) 1 commit
142
(merged to 'next' on 2019-10-30 at 8405cac984)
143
+ Documentation: fix a bunch of typos, both old and new
@@ -66,8 +156,8 @@ of the repositories listed at
156
Will cook in 'next'.
157
158
69
-* js/update-index-ignore-removal-for-skip-worktree (2019-10-29) 2 commits
70
- (merged to 'next' on 2019-10-30 at 5c7c7a6055)
159
+* js/update-index-ignore-removal-for-skip-worktree (2019-11-02) 2 commits
160
+ (merged to 'next' on 2019-11-02 at 57f7fb885f)
161
+ stash: handle staged changes in skip-worktree files correctly
162
+ update-index: optionally leave skip-worktree entries alone
163
@@ -99,7 +189,7 @@ of the repositories listed at
189
Will merge to 'next'.
190
191
102
-* dl/doc-diff-no-index-implies-exit-code (2019-10-30) 1 commit
192
+* dl/doc-diff-no-index-implies-exit-code (2019-11-02) 1 commit
193
- git-diff.txt: document return code of `--no-index`
194
195
Doc update.
@@ -113,13 +203,15 @@ of the repositories listed at
203
"git submodule" learned a subcommand "set-url".
204
205
116
-* js/vreportf-wo-buffering (2019-10-30) 1 commit
206
+* js/vreportf-wo-buffering (2019-11-02) 1 commit
207
- vreportf(): avoid relying on stdio buffering
208
209
Messages from die() etc. can be mixed up from multiple processes
210
without even line buffering on Windows, which has been worked
211
around.
212
213
+ Will merge to 'next'.
214
+
215
216
* ma/bisect-doc-sample-update (2019-10-29) 1 commit
217
- Documentation/git-bisect.txt: add --no-ff to merge command
@@ -163,76 +255,6 @@ of the repositories listed at
255
256
Will merge to 'next'.
257
166
---------------------------------------------------
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]
258
259
* hv/bitshift-constants-in-blame (2019-10-21) 1 commit
260
(merged to 'next' on 2019-10-24 at bc84aae4d4)
@@ -295,16 +317,6 @@ of the repositories listed at
317
Expecting a reroll.
318
319
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
-
305
- Will cook in 'next'.
306
-
307
-
320
* jc/am-show-current-patch-docfix (2019-10-23) 1 commit
321
(merged to 'next' on 2019-10-24 at 31fa6081f2)
322
+ doc: am --show-current-patch gives an entire e-mail message
@@ -380,15 +392,6 @@ of the repositories listed at
392
Will merge to 'next'.
393
394
383
-* jt/delay-fetch-if-missing (2019-10-24) 1 commit
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
-
389
- Will cook in 'next'.
390
-
391
-
395
* dd/notes-copy-default-dst-to-head (2019-10-18) 2 commits
396
(merged to 'next' on 2019-10-18 at 2588a175ec)
397
+ notes: fix minimum number of parameters to "copy" subcommand