Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-09 Thread Johannes Schindelin
Hi Phillip, On Thu, 8 Nov 2018, Phillip Wood wrote: > On 07/11/2018 09:41, Junio C Hamano wrote: > > 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

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-08 Thread Phillip Wood
On 07/11/2018 09:41, Junio C Hamano wrote: 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

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread Junio C Hamano
Junio C Hamano writes: >> Not surprising. The i18n series makes fsck output localized strings >> and without updating grep to test_i18ngrep, new tests will fail. If >> 'pu' was passing before, I'm ok with just ejecting this series for >> now. Then I wait for the other to land, rebase, fixup and

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread Junio C Hamano
Duy Nguyen writes: > On Wed, Nov 7, 2018 at 2:09 PM SZEDER Gábor wrote: >> >> On Wed, Nov 07, 2018 at 06:41:45PM +0900, Junio C Hamano wrote: >> > * nd/i18n (2018-11-06) 16 commits >> > - fsck: mark strings for translation >> > - fsck: reduce word legos to help i18n >> > ... >> > More

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread Duy Nguyen
On Wed, Nov 7, 2018 at 2:09 PM SZEDER Gábor wrote: > > On Wed, Nov 07, 2018 at 06:41:45PM +0900, Junio C Hamano wrote: > > * nd/i18n (2018-11-06) 16 commits > > - fsck: mark strings for translation > > - fsck: reduce word legos to help i18n > > - parse-options.c: mark more strings for

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread SZEDER Gábor
On Wed, Nov 07, 2018 at 06:41:45PM +0900, Junio C Hamano wrote: > * nd/i18n (2018-11-06) 16 commits > - fsck: mark strings for translation > - fsck: reduce word legos to help i18n > - parse-options.c: mark more strings for translation > - parse-options.c: turn some die() to BUG() > -

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread Junio C Hamano
Ævar Arnfjörð Bjarmason writes: > On Wed, Nov 07 2018, Junio C Hamano wrote: > >> * ab/range-diff-no-patch (2018-11-07) 1 commit >> - range-diff: add a --no-patch option to show a summary >> >> "range-diff" learns the "--no-patch" option, which can be used to >> get a high-level overview

Re: What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 Thread Ævar Arnfjörð Bjarmason
On Wed, Nov 07 2018, Junio C Hamano wrote: > * ab/range-diff-no-patch (2018-11-07) 1 commit > - range-diff: add a --no-patch option to show a summary > > "range-diff" learns the "--no-patch" option, which can be used to > get a high-level overview without the actual line-by-line patch >

What's cooking in git.git (Nov 2018, #03; Wed, 7)

2018-11-07 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. You can find the changes