f676aac9e9 · matheusbsbs/matheus-bagliano

@@ -1,10 +1,10 @@

1 To: git@vger.kernel.org

2 Bcc: lwn@lwn.net

3 -Subject: What's cooking in git.git (Jul 2017, #06; Thu, 20)

4 -X-master-at: 981adb928e5ebe8bbf84d80a8f8fb3a4cbc30afd

5 -X-next-at: 6ee059e2f3ee8b8553e8fe6adb297897e619ac91

3 +Subject: What's cooking in git.git (Jul 2017, #07; Mon, 24)

4 +X-master-at: 5800c63717ae35286a1441f14ffff753e01f7e2b

5 +X-next-at: 8e98c6e5c05367936b792dc40ed7cc7876e9d4c7

6

7 -What's cooking in git.git (Jul 2017, #06; Thu, 20)

7 +What's cooking in git.git (Jul 2017, #07; Mon, 24)

8 --------------------------------------------------

9

10 Here are the topics that have been cooking. Commits prefixed with

@@ -12,11 +12,14 @@ 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 -Tagging of -rc1 is delayed, waiting for a resolution on the l10n

16 -issues around '"%"PRItime' custome format specifier, which naturally

17 -cannot be handled by gettext(1) suite nicely. I think what is queued

18 -on 'pu' based on Dscho's suggestion is a usable workaround, and I

19 -plan to use it unless I hear better ideas in the comint 10+ hours.

15 +With help from Jiang, Dscho and Jean-Noël, we agreed on the way to

16 +handle i18n issues around our custom timestamp_t type and its format

17 +PRItime, and tagging of -rc1 has been delayed a bit. But now it has

18 +happened. There is a small unrelated change still cooking somewhere

19 +else that may have to go in the final release, but other than that

20 +one, no topic is expected to go from 'next' to 'master' until the

21 +final. Regression fixes and reverts are possible but let's hope

22 +there are no need for them.

23

24 You can find the changes described here in the integration branches

25 of the repositories listed at

@@ -26,109 +29,57 @@ of the repositories listed at

29 --------------------------------------------------

30 [Graduated to "master"]

31

29 -* ew/fd-cloexec-fix (2017-07-17) 1 commit

30 - (merged to 'next' on 2017-07-18 at a3de1b1998)

31 - + set FD_CLOEXEC properly when O_CLOEXEC is not supported

32 -

33 - Portability/fallback fix.

34 -

35 -

36 -* jk/build-with-asan (2017-07-17) 1 commit

37 - (merged to 'next' on 2017-07-18 at f92636c616)

38 - + Makefile: allow combining UBSan with other sanitizers

39 -

40 - A recent update made it easier to use "-fsanitize=" option while

41 - compiling but supported only one sanitize option. Allow more than

42 - one to be combined, joined with a comma, like "make SANITIZE=foo,bar".

43 -

44 -

45 -* jk/test-copy-bytes-fix (2017-07-17) 1 commit

46 - (merged to 'next' on 2017-07-18 at c32c264e96)

47 - + t: handle EOF in test_copy_bytes()

32 +* jc/po-pritime-fix (2017-07-20) 1 commit

33 + (merged to 'next' on 2017-07-21 at 61f0e3b37f)

34 + + Makefile: help gettext tools to cope with our custom PRItime format

35

49 - A test fix.

36 + We started using "%" PRItime, imitating "%" PRIuMAX and friends, as

37 + a way to format the internal timestamp value, but this does not

38 + play well with gettext(1) i18n framework, and causes "make pot"

39 + that is run by the l10n coordinator to create a broken po/git.pot

40 + file. This is a possible workaround for that problem.

41

42

52 -* js/alias-case-sensitivity (2017-07-17) 2 commits

53 - (merged to 'next' on 2017-07-18 at 31641a39f2)

54 - + alias: compare alias name *case-insensitively*

55 - + t1300: demonstrate that CamelCased aliases regressed

43 +* ks/doc-fixes (2017-07-18) 2 commits

44 + (merged to 'next' on 2017-07-20 at c34b00d0a0)

45 + + doc: reformat the paragraph containing the 'cut-line'

46 + + doc: camelCase the i18n config variables to improve readability

47

57 - A recent update broke an alias that contained an uppercase letter.

48 + Doc clean-up.

49

50

60 -* mt/p4-parse-G-output (2017-07-13) 3 commits

61 - (merged to 'next' on 2017-07-18 at e065b689d4)

62 - + git-p4: filter for {'code':'info'} in p4CmdList

63 - + git-p4: parse marshal output "p4 -G" in p4 changes

64 - + git-p4: git-p4 tests with p4 triggers

51 +* rj/cygwin-fread-reads-directories (2017-07-21) 1 commit

52 + (merged to 'next' on 2017-07-21 at 28694cf254)

53 + + config.mak.uname: set FREAD_READS_DIRECTORIES for cygwin

54

66 - Use "p4 -G" to make "p4 changes" output more Python-friendly

67 - to parse.

55 + It turns out that Cygwin also needs the fopen() wrapper that

56 + returns failure when a directory is opened for reading.

57

58 --------------------------------------------------

59 [New Topics]

60

72 -* bw/push-options-recursively-to-submodules (2017-07-20) 1 commit

73 - - submodule--helper: teach push-check to handle HEAD

61 +* js/run-process-parallel-api-fix (2017-07-21) 1 commit

62 + - run_processes_parallel: change confusing task_cb convention

63

75 - "git push --recurse-submodules $there HEAD:$target" was not

76 - propagated down to the submodules, but now it is.

64 + API fix.

65

66 Will merge to and cook in 'next'.

67

68

81 -* jc/http-sslkey-and-ssl-cert-are-paths (2017-07-20) 1 commit

82 - (merged to 'next' on 2017-07-20 at 5489304b99)

83 - + http.c: http.sslcert and http.sslkey are both pathnames

84 -

85 - The http.{sslkey,sslCert} configuration variables are to be

86 - interpreted as a pathname that honors "~[username]/" prefix, but

87 - weren't, which has been fixed.

88 -

89 - Will cook in 'next'.

90 -

69 +* cc/ref-is-hidden-microcleanup (2017-07-24) 1 commit

70 + - refs: use skip_prefix() in ref_is_hidden()

71

92 -* jc/po-pritime-fix (2017-07-20) 1 commit

93 - - Makefile: help gettext tools to cope with our custom PRItime format

94 -

95 - We started using "%" PRItime, imitating "%" PRIuMAX and friends, as

96 - a way to format the internal timestamp value, but this does not

97 - play well with gettext(1) i18n framework, and causes "make pot"

98 - that is run by the l10n coordinator to create a broken po/git.pot

99 - file. This is a possible workaround for that problem.

100 -

101 - Will fast-track to 2.14-rc1 once we hear positive result.

102 -

103 -

104 -* jt/fsck-code-cleanup (2017-07-20) 2 commits

105 - (merged to 'next' on 2017-07-20 at f7045a8c47)

106 - + object: remove "used" field from struct object

107 - + fsck: remove redundant parse_tree() invocation

108 -

109 - Code clean-up.

110 -

111 - Will cook in 'next'.

72 + Code cleanup.

73

74 + Will merge to and cook in 'next'.

75

114 -* rs/pack-objects-pbase-cleanup (2017-07-20) 1 commit

115 - (merged to 'next' on 2017-07-20 at a6b618559b)

116 - + pack-objects: remove unnecessary NULL check

76

118 - Code clean-up.

77 +* js/blame-lib (2017-07-24) 1 commit

78 + - blame: fix memory corruption scrambling revision name in error message

79

120 - Will cook in 'next'.

80 + A hotfix to a topic already in 'master'.

81

122 -

123 -* st/lib-gpg-kill-stray-agent (2017-07-20) 1 commit

124 - (merged to 'next' on 2017-07-20 at 8ea68c483f)

125 - + t: lib-gpg: flush gpg agent on startup

126 -

127 - Some versions of GnuPG fails to kill gpg-agent it auto-spawned

128 - and such a left-over agent can interfere with a test. Work it

129 - around by attempting to kill one before starting a new test.

130 -

131 - Will cook in 'next'.

82 + Will merge to 'next'.

83

84 --------------------------------------------------

85 [Stalled]

@@ -196,6 +147,56 @@ of the repositories listed at

147 --------------------------------------------------

148 [Cooking]

149

150 +* bw/push-options-recursively-to-submodules (2017-07-20) 1 commit

151 + - submodule--helper: teach push-check to handle HEAD

152 +

153 + "git push --recurse-submodules $there HEAD:$target" was not

154 + propagated down to the submodules, but now it is.

155 +

156 + Will merge to and cook in 'next'.

157 +

158 +

159 +* jc/http-sslkey-and-ssl-cert-are-paths (2017-07-20) 1 commit

160 + (merged to 'next' on 2017-07-20 at 5489304b99)

161 + + http.c: http.sslcert and http.sslkey are both pathnames

162 +

163 + The http.{sslkey,sslCert} configuration variables are to be

164 + interpreted as a pathname that honors "~[username]/" prefix, but

165 + weren't, which has been fixed.

166 +

167 + Will cook in 'next'.

168 +

169 +

170 +* jt/fsck-code-cleanup (2017-07-20) 2 commits

171 + (merged to 'next' on 2017-07-20 at f7045a8c47)

172 + + object: remove "used" field from struct object

173 + + fsck: remove redundant parse_tree() invocation

174 +

175 + Code clean-up.

176 +

177 + Will cook in 'next'.

178 +

179 +

180 +* rs/pack-objects-pbase-cleanup (2017-07-20) 1 commit

181 + (merged to 'next' on 2017-07-20 at a6b618559b)

182 + + pack-objects: remove unnecessary NULL check

183 +

184 + Code clean-up.

185 +

186 + Will cook in 'next'.

187 +

188 +

189 +* st/lib-gpg-kill-stray-agent (2017-07-20) 1 commit

190 + (merged to 'next' on 2017-07-20 at 8ea68c483f)

191 + + t: lib-gpg: flush gpg agent on startup

192 +

193 + Some versions of GnuPG fails to kill gpg-agent it auto-spawned

194 + and such a left-over agent can interfere with a test. Work it

195 + around by attempting to kill one before starting a new test.

196 +

197 + Will cook in 'next'.

198 +

199 +

200 * jk/c99 (2017-07-18) 2 commits

201 (merged to 'next' on 2017-07-18 at 1cfc30f7c1)

202 + clean.c: use designated initializer

@@ -249,16 +250,6 @@ of the repositories listed at

250 Will merge to and cook in 'next'.

251

252

252 -* ks/doc-fixes (2017-07-18) 2 commits

253 - (merged to 'next' on 2017-07-20 at c34b00d0a0)

254 - + doc: reformat the paragraph containing the 'cut-line'

255 - + doc: camelCase the i18n config variables to improve readability

256 -

257 - Doc clean-up.

258 -

259 - Will merge to 'master'.

260 -

261 -

253 * rs/bswap-ubsan-fix (2017-07-17) 2 commits

254 (merged to 'next' on 2017-07-20 at ce6bad07b0)

255 + bswap: convert get_be16, get_be32 and put_be32 to inline functions

What's cooking (2017/07 #07)