Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Hi Junio, On Tue, 10 May 2016, Junio C Hamano wrote: > Johannes Schindelin writes: > > > On Fri, 6 May 2016, Junio C Hamano wrote: > > > > 2) I was under the impression that we preferred test_i18ngrep over grep... > > Only when the strings we are expecting are

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

> On 10 May 2016, at 07:52, Johannes Schindelin > wrote: > > Hi Junio, > > On Fri, 6 May 2016, Junio C Hamano wrote: > >> * jk/submodule-c-credential (2016-05-06) 6 commits >> - submodule: stop sanitizing config options >> - submodule: use

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Lars Schneider writes: > A version with at least one section error is here: > http://article.gmane.org/gmane.comp.version-control.git/293521 > Should I fix and reroll this patch? I just compared this with jc/linkgit-fix, which was done until the script introduced by

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Johannes Schindelin writes: > On Fri, 6 May 2016, Junio C Hamano wrote: > >> * jc/fsck-nul-in-commit (2016-04-14) 2 commits >> - fsck: detect and warn a commit with embedded NUL >> - fsck_commit_buffer(): do not special case the last validation >> >> "git fsck"

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Lars Schneider writes: >> On 07 May 2016, at 00:46, Junio C Hamano wrote: >> >> [...] >> >> >> * jc/doc-lint (2016-05-04) 2 commits >> - Documentation: fix linkgit references >> - ci: validate "gitlink:" in documentation > > The first patch

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

> On 07 May 2016, at 00:46, Junio C Hamano wrote: > > [...] > > > * jc/doc-lint (2016-05-04) 2 commits > - Documentation: fix linkgit references > - ci: validate "gitlink:" in documentation The first patch "Documentation: fix linkgit references" seems not to be on the

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Hi Junio, On Fri, 6 May 2016, Junio C Hamano wrote: > * jc/fsck-nul-in-commit (2016-04-14) 2 commits > - fsck: detect and warn a commit with embedded NUL > - fsck_commit_buffer(): do not special case the last validation > > "git fsck" learned to catch NUL byte in a commit object as >

Re: What's cooking in git.git (May 2016, #02; Fri, 6)

Hi Junio, On Fri, 6 May 2016, Junio C Hamano wrote: > * jk/submodule-c-credential (2016-05-06) 6 commits > - submodule: stop sanitizing config options > - submodule: use prepare_submodule_repo_env consistently > - submodule--helper: move config-sanitizing to submodule.c > - submodule: export

What's cooking in git.git (May 2016, #02; Fri, 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. The 'master' branch now has the