Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

Martin Ågren writes: >> Is this ready for 'next'? > > I am not aware of any open questions or issues. You thought out loud > about how the series was structured, in particular about introducing a > successful test, then redefining it, as opposed to introducing it as a >

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

On Fri, Mar 9, 2018 at 1:15 PM, Martin Ågren wrote: > On 7 March 2018 at 00:34, Junio C Hamano wrote: > >> * ma/config-page-only-in-list-mode (2018-02-21) 3 commits >> - config: change default of `pager.config` to "on" >> - config: respect

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

On 7 March 2018 at 00:34, Junio C Hamano wrote: > * ma/config-page-only-in-list-mode (2018-02-21) 3 commits > - config: change default of `pager.config` to "on" > - config: respect `pager.config` in list/get-mode only > - t7006: add tests for how git config paginates > >

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

> It would be great to have this rebooted now that my perl cleanup efforts > have un-blocked this. Will be happy to help review & test the next > iteration. Yes, I was just thinking the same thing. I wanted to make sure the Perl changes had landed, and I'm pleased to see that they have. I should

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

On Wed, Mar 07 2018, Johannes Schindelin jotted: > Hi Dan, > > On Tue, 6 Mar 2018, Junio C Hamano wrote: > >> * dj/runtime-prefix (2017-12-05) 4 commits >> . exec_cmd: RUNTIME_PREFIX on some POSIX systems >> . Makefile: add Perl runtime prefix support >> . Makefile: add support for

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

Hi Dan, On Tue, 6 Mar 2018, Junio C Hamano wrote: > * dj/runtime-prefix (2017-12-05) 4 commits > . exec_cmd: RUNTIME_PREFIX on some POSIX systems > . Makefile: add Perl runtime prefix support > . Makefile: add support for "perllibdir" > . Makefile: generate Perl header from template file >

What's cooking in git.git (Mar 2018, #02; Tue, 6)

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 haven't seen enough reviews