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

Re: error: core.autocrlf=input conflicts with core.eol=crlf

From
ASAlex Stangl <alex@stangl.us>
Date
Dec 5, 2014, 16:33 UTC
Message-ID
<20141205163358.GA77231@scout.stangl.us>
In-Reply-To
<5481D587.2050103@web.de>
On Fri, Dec 05, 2014 at 04:55:51PM +0100, Torsten B?gershausen wrote:
> On 12/05/2014 09:10 AM, Torsten B?gershausen wrote:
> Or a test case showing the problem is welcome too.

I mentioned some examples in my previous post. Here they are in condensed form. They assume core.eol isn't set in your global config.

These work fine: $ mkdir -p /tmp/ex1_$$;cd /tmp/ex1_$$;git init;git config --global core.autocrlf input;git config core.autocrlf false;git config core.eol crlf;git status $ mkdir -p /tmp/ex3_$$;cd /tmp/ex3_$$;git init;git config --global core.autocrlf input;git -c core.autocrlf=false -c core.eol=crlf status

These equivalents fail: $ mkdir -p /tmp/ex2_$$;cd /tmp/ex2_$$;git init;git config --global core.autocrlf input;git config core.eol crlf;git config core.autocrlf false;git status $ mkdir -p /tmp/ex4_$$;cd /tmp/ex4_$$;git init;git config --global core.autocrlf input;git -c core.eol=crlf -c core.autocrlf=false status

Alex
Previous: Torsten Bögershausen
Message 3 of 3 in “error: core.autocrlf=input conflicts with core.eol=crlf”
  1. Alex StanglDec 5, 2014
  2. Torsten BögershausenDec 5, 2014
  3. Alex StanglDec 5, 2014

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.