86dd879b3a · matheusbsbs/matheus-bagliano

@@ -1,243 +1,68 @@

1 To: git@vger.kernel.org

2 Bcc: lwn@lwn.net

3 -Subject: What's cooking in git.git (Sep 2013, #06; Fri, 20)

3 +Subject: What's cooking in git.git (Sep 2013, #07; Mon, 23)

4 X-master-at: 128a96c98442524c7f2eeef4757b1e48445f24ce

5 X-next-at: 0d6e0ce2a5090eb3c05a624d1ad584a1153fcc52

6

7 -What's cooking in git.git (Sep 2013, #06; Fri, 20)

7 +What's cooking in git.git (Sep 2013, #07; Mon, 23)

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

9

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

11 '-' are only in 'pu' (proposed updates) while commits prefixed with

12 '+' are in 'next'.

13

14 -The fifth batch of topics are in 'master'. We are about to pass 350

15 -non-merge commits since the last release, which means we are about

16 -halfway there for the next one. Among ~60 contributors who have

17 -commits in the 'master' branch since v1.8.4, ~10 are new faces.

14 +The fifth batch of topics are in 'master'.

15

19 -I'll be offline starting next week for a few weeks; in order to

20 -improve the "bus factor", I asked Jonathan Nieder to fill in for me

21 -as an interim maintainer, with Peff as a back-up.

16 +You can find the changes described here in the integration branches at

17

23 -You can find the changes described here in the integration branches

24 -of the repositories listed at

18 + https://repo.or.cz/r/git/jrn.git

19

26 - http://git-blame.blogspot.com/p/git-public-repositories.html

27 -

28 ---------------------------------------------------

29 -[Graduated to "master"]

30 -

31 -* bc/http-backend-allow-405 (2013-09-12) 1 commit

32 - (merged to 'next' on 2013-09-12 at bc1719f)

33 - + http-backend: provide Allow header for 405

34 -

35 - When the webserver responds with "405 Method Not Allowed", it

36 - should tell the client what methods are allowed with the "Allow"

37 - header.

38 -

39 -

40 -* bk/refs-multi-update (2013-09-11) 8 commits

41 - (merged to 'next' on 2013-09-13 at e6d21af)

42 - + update-ref: add test cases covering --stdin signature

43 - + update-ref: support multiple simultaneous updates

44 - + refs: add update_refs for multiple simultaneous updates

45 - + refs: add function to repack without multiple refs

46 - + refs: factor delete_ref loose ref step into a helper

47 - + refs: factor update_ref steps into helpers

48 - + refs: report ref type from lock_any_ref_for_update

49 - + reset: rename update_refs to reset_refs

50 -

51 - Give "update-refs" a "--stdin" option to read multiple update

52 - requests and perform them in an all-or-none fashion.

53 -

54 -

55 -* dw/check-ignore-sans-index (2013-09-12) 1 commit

56 - (merged to 'next' on 2013-09-13 at 8daec3c)

57 - + check-ignore: Add option to ignore index contents

58 -

59 - "git check-ignore" follows the same rule as "git add" and "git

60 - status" in that the ignore/exclude mechanism does not take effect

61 - on paths that are already tracked. With "--no-index" option, it

62 - can be used to diagnose which paths that should have been ignored

63 - have been mistakenly added to the index.

64 -

65 -

66 -* fc/at-head (2013-09-12) 2 commits

67 - (merged to 'next' on 2013-09-13 at d3800c2)

68 - + Add new @ shortcut for HEAD

69 - + sha1-name: pass len argument to interpret_branch_name()

70 -

71 - Attempt to resurrect "Type @ for HEAD"; the bottom one seems to be

72 - a genuine code improvement, but identifying cases where "@" means

73 - HEAD were harder than it should have been. I think the result of

74 - squashing the tip one in covers all the necessary cases.

75 -

76 -

77 -* hu/cherry-pick-previous-branch (2013-09-09) 1 commit

78 - (merged to 'next' on 2013-09-12 at 36e4d9b)

79 - + cherry-pick: allow "-" as abbreviation of '@{-1}'

80 -

81 - Just like "git checkout -" knows to check out and "git merge -"

82 - knows to merge the branch you were previously on, teach "git

83 - cherry-pick" to understand "-" as the previous branch.

84 -

85 -

86 -* jh/checkout-auto-tracking (2013-09-17) 6 commits

87 - (merged to 'next' on 2013-09-17 at 6748f49)

88 - + t3200: fix failure on case-insensitive filesystems

89 - (merged to 'next' on 2013-09-13 at 2aa1553)

90 - + branch.c: Relax unnecessary requirement on upstream's remote ref name

91 - + t3200: Add test demonstrating minor regression in 41c21f2

92 - + Refer to branch.<name>.remote/merge when documenting --track

93 - + t3200: Minor fix when preparing for tracking failure

94 - + t2024: Fix &&-chaining and a couple of typos

95 -

96 - Fix a minor regression in v1.8.3.2 and later that made it

97 - impossible to base your local work on anything but a local branch

98 - of the upstream repository you are tracking from.

99 -

100 -

101 -* jk/upload-pack-keepalive (2013-09-09) 2 commits

102 - (merged to 'next' on 2013-09-17 at d3141ac)

103 - + upload-pack: bump keepalive default to 5 seconds

104 - + upload-pack: send keepalive packets during pack computation

105 -

106 - When running "fetch -q", a long silence while the sender side

107 - computes the set of objects to send can be mistaken by proxies as

108 - dropped connection.

109 -

110 -

111 -* jx/branch-vv-always-compare-with-upstream (2013-08-26) 2 commits

112 - (merged to 'next' on 2013-09-12 at b5c37f4)

113 - + status: always show tracking branch even no change

114 - + branch: report invalid tracking branch as gone

115 -

116 - "git branch -v -v" (and "git status") did not distinguish among a

117 - branch that does not build on any other branch, a branch that is in

118 - sync with the branch it builds on, and a branch that is configured

119 - to build on some other branch that no longer exists.

120 -

121 -

122 -* mm/commit-template-squelch-advice-messages (2013-09-12) 3 commits

123 - (merged to 'next' on 2013-09-13 at 410d207)

124 - + commit: disable status hints when writing to COMMIT_EDITMSG

125 - + wt-status: turn advice_status_hints into a field of wt_status

126 - + commit: factor status configuration is a helper function

127 -

128 - From the commit log template, remove irrelevant "advice" messages

129 - that are shared with "git status" output.

130 -

131 -

132 -* mm/rebase-continue-freebsd-WB (2013-09-09) 1 commit

133 - (merged to 'next' on 2013-09-13 at 82e8b91)

134 - + rebase: fix run_specific_rebase's use of "return" on FreeBSD

135 -

136 - Work around a bug in FreeBSD shell that caused a regression to "git

137 - rebase" in v1.8.4. May need to be later applied to 'maint'.

20 +I am still catching up on patches sent since last week. If I have

21 +missed yours, do not despair, but feel free to send me a reminder to

22 +look at it.

23

139 -

140 -* mm/status-without-comment-char (2013-09-17) 7 commits

141 - (merged to 'next' on 2013-09-17 at d93e7c1)

142 - + t7508: avoid non-portable sed expression

143 - (merged to 'next' on 2013-09-12 at 89161b8)

144 - + status: add missing blank line after list of "other" files

145 - + tests: don't set status.displayCommentPrefix file-wide

146 - + status: disable display of '#' comment prefix by default

147 - + submodule summary: ignore --for-status option

148 - + wt-status: use argv_array API

149 - + builtin/stripspace.c: fix broken indentation

150 -

151 - Allow "git status" to omit the prefix to make its output a comment

152 - in a commit log editor, which is not necessary for human

153 - consumption.

154 -

155 - We may want to tighten the output to omit unnecessary trailing

156 - blank lines, but that does not have to be in the scope of this

157 - series.

158 -

159 -

160 -* nd/fetch-into-shallow (2013-08-28) 7 commits

161 - (merged to 'next' on 2013-09-09 at 87a3b99)

162 - + Add testcase for needless objects during a shallow fetch

163 - + list-objects: mark more commits as edges in mark_edges_uninteresting

164 - + list-objects: reduce one argument in mark_edges_uninteresting

165 - + upload-pack: delegate rev walking in shallow fetch to pack-objects

166 - + shallow: add setup_temporary_shallow()

167 - + shallow: only add shallow graft points to new shallow file

168 - + move setup_alternate_shallow and write_shallow_commits to shallow.c

169 -

170 - When there is no sufficient overlap between old and new history

171 - during a fetch into a shallow repository, we unnecessarily sent

172 - objects the sending side knows the receiving end has.

173 -

174 -

175 -* np/lookup-object-hashing (2013-09-11) 1 commit

176 - (merged to 'next' on 2013-09-12 at d835ef6)

177 - + lookup_object: remove hashtable_index() and optimize hash_obj()

178 -

179 - Micro optimize hash function used in the object hash table.

180 -

181 -

182 -* nr/git-cd-to-a-directory (2013-09-19) 2 commits

183 - (merged to 'next' on 2013-09-19 at e9394e8)

184 - + t0056: "git -C" test updates

185 - (merged to 'next' on 2013-09-13 at 2b07af9)

186 - + git: run in a directory given with -C option

187 -

188 - Just like "make -C <directory>", make "git -C <directory> ..." to

189 - go there before doing anything else.

190 -

191 -

192 -* rh/peeling-tag-to-tag (2013-09-03) 2 commits

193 - (merged to 'next' on 2013-09-12 at 3a1d906)

194 - + peel_onion: do not assume length of x_type globals

195 - + peel_onion(): add support for <rev>^{tag}

196 -

197 - Make "foo^{tag}" to peel a tag to itself, i.e. no-op., and fail if

198 - "foo" is not a tag.

24 +For those following along at home, the process used to build this

25 +message is described in Documentation/howto/maintain-git.txt. Maybe

26 +some day someone will tweak the tools so they can be used by other

27 +projects and more than a few people will know how to use them (hint,

28 +hint). In the meantime the documentation has been serving well as a

29 +teacher.

30

31 --------------------------------------------------

32 [New Topics]

33

203 -* jc/revision-range-unpeel (2013-09-20) 2 commits

204 - - (possible fixup) jc/revision-range-unpeel - peel only when necessary

205 - - revision: do not peel tags used in range notation

206 -

207 - "git rev-list --objects ^v1.0^ v1.0" gave v1.0 tag itself in the

208 - output, but "git rev-list --objects v1.0^..v1.0" did not.

209 -

210 - Need to decide either squashing the top fixup in, or dropping it

211 - and then merge to 'next'.

212 -

213 -

214 -* tg/perf-lib-test-perf-cleanup (2013-09-19) 2 commits

215 - - perf-lib: add test_perf_cleanup target

216 - - perf-lib: split starting the test from the execution

217 -

218 - Add test_perf_cleanup shell function to the perf suite, that allows

219 - the script writers to define a test with a clean-up action.

220 -

221 - Will hold, until we get any user.

222 -

223 -

224 -* jc/push-cas (2013-09-20) 1 commit

225 - (merged to 'next' on 2013-09-20 at 5e1e7cc)

226 - + t5541: mark passing c-a-s test as success

227 -

228 - A trivial fix to a test.

229 -

230 - Will merge to 'master'.

231 -

232 -

233 -* jk/format-patch-from (2013-09-20) 1 commit

234 - (merged to 'next' on 2013-09-20 at 0506530)

235 - + format-patch: print in-body "From" only when needed

236 -

237 - "format-patch --from=<whom>" forgot to omit unnecessary in-body

238 - from line, i.e. when <whom> is the same as the real author.

239 -

240 - Will merge to 'master'.

34 +* bc/gnome-keyring (2013-09-23) 15 commits

35 + - contrib/git-credential-gnome-keyring.c: support really ancient gnome-keyring

36 + - contrib/git-credential-gnome-keyring.c: support ancient gnome-keyring

37 + - contrib/git-credential-gnome-keyring.c: report failure to store password

38 + - contrib/git-credential-gnome-keyring.c: use glib messaging functions

39 + - contrib/git-credential-gnome-keyring.c: use glib memory allocation functions

40 + - contrib/git-credential-gnome-keyring.c: use secure memory for reading passwords

41 + - contrib/git-credential-gnome-keyring.c: use secure memory functions for passwds

42 + - contrib/git-credential-gnome-keyring.c: use gnome helpers in keyring_object()

43 + - contrib/git-credential-gnome-keyring.c: ensure buffer is non-empty before accessing

44 + - contrib/git-credential-gnome-keyring.c: strlen() returns size_t, not ssize_t

45 + - contrib/git-credential-gnome-keyring.c: set Gnome application name

46 + - contrib/git-credential-gnome-keyring.c: exit non-zero when called incorrectly

47 + - contrib/git-credential-gnome-keyring.c: add static where applicable

48 + - contrib/git-credential-gnome-keyring.c: remove unused die() function

49 + - contrib/git-credential-gnome-keyring.c: remove unnecessary pre-declarations

50 +

51 + Cleanups and tweaks for credential handling to work with ancient versions

52 + of the gnome-keyring library that are still in use.

53 +

54 + This is version 1 of the series, to give it more exposure. Waiting for

55 + the series to stabilize before including in 'next'.

56 +

57 +

58 +* bp/mediawiki-infinite-loop-fix (2013-09-23) 1 commit

59 + - git-remote-mediawiki: bugfix for pages w/ >500 revisions

60 +

61 + The mediawiki:: remote helper would hang while handling results from

62 + queries with more than 500 results against version 1.21 or newer of

63 + the Mediawiki server.

64 +

65 + Will merge to 'maint'.

66

67 --------------------------------------------------

68 [Stalled]

@@ -247,7 +72,7 @@ of the repositories listed at

72 - merge-recursive: untangle double meaning of o->call_depth

73 - merge-recursive: remove dead conditional in update_stages()

74

250 - Will hold, until we get any user.

75 + Will hold until there is a caller to learn from.

76

77

78 * jc/ref-excludes (2013-09-03) 2 commits

@@ -307,8 +132,9 @@ of the repositories listed at

132 Make "git grep" and "git show" pay attention to --textconv when

133 dealing with blob objects.

134

310 - I thought this was pretty well designed and executed, but it seems

311 - there are some doubts on the list; kicked back to 'pu'.

135 + There was a question about how defaulting to 'git show --textconv'

136 + would interact with the "git show HEAD:file.c >file.c" habit.

137 + $gmane/221833

138

139

140 * jc/format-patch (2013-04-22) 2 commits

@@ -321,11 +147,6 @@ of the repositories listed at

147 stripping out more MIMEy stuff are left as exercises to interested

148 parties.

149

324 - Not ready for inclusion.

325 -

326 - Will discard unless we hear from anybody who is interested in

327 - tying its loose ends.

328 -

150

151 * jk/gitweb-utf8 (2013-04-08) 4 commits

152 - gitweb: Fix broken blob action parameters on blob/commitdiff pages

@@ -351,6 +172,46 @@ of the repositories listed at

172 --------------------------------------------------

173 [Cooking]

174

175 +* jc/revision-range-unpeel (2013-09-20) 2 commits

176 + - (possible fixup) jc/revision-range-unpeel - peel only when necessary

177 + - revision: do not peel tags used in range notation

178 +

179 + "git rev-list --objects ^v1.0^ v1.0" gave v1.0 tag itself in the

180 + output, but "git rev-list --objects v1.0^..v1.0" did not.

181 +

182 + Need to decide either squashing the top fixup in, or dropping it

183 + and then merge to 'next'.

184 +

185 +

186 +* tg/perf-lib-test-perf-cleanup (2013-09-19) 2 commits

187 + - perf-lib: add test_perf_cleanup target

188 + - perf-lib: split starting the test from the execution

189 +

190 + Add test_perf_cleanup shell function to the perf suite, that allows

191 + the script writers to define a test with a clean-up action.

192 +

193 + Holding until needed.

194 +

195 +

196 +* jc/push-cas (2013-09-20) 1 commit

197 + (merged to 'next' on 2013-09-20 at 5e1e7cc)

198 + + t5541: mark passing c-a-s test as success

199 +

200 + A trivial fix to a test.

201 +

202 + Will merge to 'master'.

203 +

204 +

205 +* jk/format-patch-from (2013-09-20) 1 commit

206 + (merged to 'next' on 2013-09-20 at 0506530)

207 + + format-patch: print in-body "From" only when needed

208 +

209 + "format-patch --from=<whom>" forgot to omit unnecessary in-body

210 + from line, i.e. when <whom> is the same as the real author.

211 +

212 + Will merge to 'master'.

213 +

214 +

215 * es/name-hash-no-trailing-slash-in-dirs (2013-09-17) 4 commits

216 (merged to 'next' on 2013-09-20 at 9633d9a)

217 + dir: revert work-around for retired dangerous behavior

What's cooking (2013/09 #07)