Re: What's cooking in git.git (Dec 2017, #01; Mon, 4)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Dec 7, 2017, 15:48 UTC
- Message-ID
- <alpine.DEB.2.21.1.1712071643410.4318@virtualbox>
- In-Reply-To
- <DA960DCE-0635-47CF-B3C4-8133021799F1@gmail.com>
Hi,
On Wed, 6 Dec 2017, Lars Schneider wrote:
Show 17 quoted lines
> > > On 04 Dec 2017, at 22:46, Junio C Hamano <gitster@pobox.com> wrote: > > > > > > * tb/check-crlf-for-safe-crlf (2017-11-27) 1 commit > > - convert: tighten the safe autocrlf handling > > > > The "safe crlf" check incorrectly triggered for contents that does > > not use CRLF as line endings, which has been corrected. > > > > Will merge to 'next'. > > > > Looks like t0027-auto-crlf.sh is failing on Windows: > https://travis-ci.org/git/git/jobs/312135514 > > Could that patch be related?
That is not the only thing going wrong:
https://travis-ci.org/git/git/builds/312551566
It would seem that t9001 is broken on Linux32, t5616 is broken on macOS, and something really kinky is going on with the GETTEXT_POISON text, as it seems to just abort while trying to run t6120.
Ciao, Johannes