git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Dec 2017, #02; Thu, 7)

From
Torsten Bögershausen <tboegi@web.de>
Date
Dec 8, 2017, 05:49 UTC
Message-ID
<20171208054934.GA17893@tor.lan>
In-Reply-To
<xmqqfu8me7ot.fsf@gitster.mtv.corp.google.com>
Show 9 quoted lines
> * tb/check-crlf-for-safe-crlf (2017-11-27) 1 commit
>   (merged to 'next' on 2017-12-05 at 7adaa1fe01)
>  + 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.
> 
>  Broken on Windows???
>  cf. <DA960DCE-0635-47CF-B3C4-8133021799F1@gmail.com>
Yes, broken on Windows. A fix is coming the next days.
Previous: Junio C HamanoNext: Johannes Schindelin
Message 2 of 9 in “What's cooking in git.git (Dec 2017, #02; Thu, 7)”
  1. Junio C HamanoDec 7, 2017
  2. Torsten BögershausenDec 8, 2017
  3. Johannes SchindelinDec 8, 2017
  4. Junio C HamanoDec 8, 2017
  5. Christian CouderDec 8, 2017
  6. Junio C HamanoDec 8, 2017
  7. Christian CouderDec 12, 2017
  8. Philip OakleyDec 12, 2017
  9. Jeff HostetlerDec 13, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.