083378cc35 · matheusbsbs/matheus-bagliano

@@ -39,6 +39,16 @@ UI, Workflows & Features

39 option of "git rebase" can take its argument as the value of the

40 option.

41

42 + * The userdiff machinery has been taught that "async def" is another

43 + way to begin a "function" in Python.

44 +

45 + * "git range-diff" learned to take the "--notes=<ref>" and the

46 + "--no-notes" options to control the commit notes included in the

47 + log message that gets compared.

48 +

49 + * "git rev-parse --show-toplevel" run outside of any working tree did

50 + not error out, which has been corrected.

51 +

52

53 Performance, Internal Implementation, Development Support etc.

54

@@ -66,6 +76,33 @@ Performance, Internal Implementation, Development Support etc.

76 * Handling of commit objects that use non UTF-8 encoding during

77 "rebase -i" has been improved.

78

79 + * The beginning of rewriting "git add -i" in C.

80 +

81 + * A label used in the todo list that are generated by "git rebase

82 + --rebase-merges" is used as a part of a refname; the logic to come

83 + up with the label has been tightened to avoid names that cannot be

84 + used as such.

85 +

86 + * The logic to avoid duplicate label names generated by "git rebase

87 + --rebase-merges" forgot that the machinery itself uses "onto" as a

88 + label name, which must be avoided by auto-generated labels, which

89 + has been corrected.

90 +

91 + * We have had compatibility fallback macro definitions for "PRIuMAX",

92 + "PRIu32", etc. but did not for "PRIdMAX", while the code used the

93 + last one apparently without any hiccup reported recently. The

94 + fallback macro definitions for these <inttypes.h> macros that must

95 + appear in C99 systems have been removed.

96 +

97 + * Recently we have declared that GIT_TEST_* variables take the

98 + usual boolean values (it used to be that some used "non-empty

99 + means true" and taking GIT_TEST_VAR=YesPlease as true); make

100 + sure we notice and fail when non-bool strings are given to

101 + these variables.

102 +

103 + * Users of oneway_merge() (like "reset --hard") learned to take

104 + advantage of fsmonitor to avoid unnecessary lstat(2) calls.

105 +

106

107 Fixes since v2.24

108 -----------------

@@ -139,6 +176,45 @@ Fixes since v2.24

176 based on end-user input have been corrected.

177 (merge a376e37b2c jk/gitweb-anti-xss later to maint).

178

179 + * CI jobs for macOS has been made less chatty when updating perforce

180 + package used during testing.

181 + (merge 0dbc4a0edf jc/azure-ci-osx-fix-fix later to maint).

182 +

183 + * "git unpack-objects" used to show progress based only on the number

184 + of received and unpacked objects, which stalled when it has to

185 + handle an unusually large object. It now shows the throughput as

186 + well.

187 + (merge bae60ba7e9 sg/unpack-progress-throughput later to maint).

188 +

189 + * The sequencer machinery compared the HEAD and the state it is

190 + attempting to commit to decide if the result would be a no-op

191 + commit, even when amending a commit, which was incorrect, and

192 + has been corrected.

193 +

194 + * The code to parse GPG output used to assume incorrectly that the

195 + finterprint for the primary key would always be present for a valid

196 + signature, which has been corrected.

197 + (merge 67a6ea6300 hi/gpg-optional-pkfp-fix later to maint).

198 +

199 + * "git submodule status" and "git submodule status --cached" show

200 + different things, but the documentation did not cover them

201 + correctly, which has been corrected.

202 + (merge 8d483c8408 mg/doc-submodule-status-cached later to maint).

203 +

204 + * "git reset --patch $object" without any pathspec should allow a

205 + tree object to be given, but incorrectly required a committish,

206 + which has been corrected.

207 +

208 + * "git submodule status" that is run from a subdirectory of the

209 + superproject did not work well, which has been corrected.

210 + (merge 1f3aea22c7 mg/submodule-status-from-a-subdirectory later to maint).

211 +

212 + * The revision walking machinery uses resources like per-object flag

213 + bits that need to be reset before a new iteration of walking

214 + begins, but the resources related to topological walk were not

215 + cleared correctly, which has been corrected.

216 + (merge 0aa0c2b2ec mh/clear-topo-walk-upon-reset later to maint).

217 +

218 * Other code cleanup, docfix, build fix, etc.

219 (merge 80736d7c5e jc/am-show-current-patch-docfix later to maint).

220 (merge 8b656572ca sg/commit-graph-usage-fix later to maint).

@@ -153,3 +229,8 @@ Fixes since v2.24

229 (merge 51bd6be32d rs/use-copy-array-in-mingw-shell-command-preparation later to maint).

230 (merge b018719927 ma/t7004 later to maint).

231 (merge 932757b0cc ar/install-doc-update-cmds-needing-the-shell later to maint).

232 + (merge 46efd28be1 ep/guard-kset-tar-headers later to maint).

233 + (merge 9e5afdf997 ec/fetch-mark-common-refs-trace2 later to maint).

234 + (merge f0e58b3fe8 pb/submodule-update-fetches later to maint).

235 + (merge 2a02262078 dl/t5520-cleanup later to maint).

236 + (merge a4fb016ba1 js/pkt-line-h-typofix later to maint).

The third batch