Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Junio C Hamano
Taylor Blau writes: > It may make sense to send my other series to 'master' as well > ("ref-filter.c: pass empty-string as NULL to atom parsers"). Thanks for reminding. I was involved in the review and remember that everybody was happy with the direction. The topic was left

Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Taylor Blau
On Wed, Oct 04, 2017 at 05:46:21PM +0900, Junio C Hamano wrote: > Jeff King writes: > > >> - pretty.c: delimit "%(trailers)" arguments with "," > >> > >> "git for-each-ref --format=..." learned a new format element, > >> %(trailers), to show only the commit log trailer part of

Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Junio C Hamano
Jeff King writes: >> - pretty.c: delimit "%(trailers)" arguments with "," >> >> "git for-each-ref --format=..." learned a new format element, >> %(trailers), to show only the commit log trailer part of the log >> message. >> >> Will merge to 'next'. > > I think we want the

Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Jeff King
On Wed, Oct 04, 2017 at 04:19:52PM +0900, Junio C Hamano wrote: > I wanted to do v2.15-rc0 today but it seems that this has to slip, > with too many topics still in flight in 'next' among which many are > fixes, one is even a fix for a recent regression. You probably already figured this out,

Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Jeff King
On Wed, Oct 04, 2017 at 04:02:12AM -0400, Jeff King wrote: > On Wed, Oct 04, 2017 at 04:19:52PM +0900, Junio C Hamano wrote: > > > * jt/partial-clone-lazy-fetch (2017-10-02) 18 commits > [...] > > The merge of this topic into jch (at 766f92478b0) causes the test suite > to fail when compiled

Re: What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Jeff King
On Wed, Oct 04, 2017 at 04:19:52PM +0900, Junio C Hamano wrote: > * jt/partial-clone-lazy-fetch (2017-10-02) 18 commits > - fetch-pack: restore save_commit_buffer after use > - unpack-trees: batch fetching of missing blobs > - clone: configure blobmaxbytes in created repos > - clone: support

What's cooking in git.git (Oct 2017, #01; Wed, 4)

2017-10-04 Thread Junio C Hamano
Here are the topics that have been cooking. Commits prefixed with '-' are only in 'pu' (proposed updates) while commits prefixed with '+' are in 'next'. The ones marked with '.' do not appear in any of the integration branches, but I am still holding onto them. I wanted to do v2.15-rc0 today