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

Re: [PATCH v8] ls-files: Add eol diagnostics

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 30, 2015, 21:45 UTC
Message-ID
<xmqqsi2jd309.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<5683E8B4.7040005@ramsayjones.plus.com>
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
Show 17 quoted lines
>> +	Show line endings ("eolinfo") and the text/eol attributes ("texteolattr") of
>> files.
>> +	"eolinfo" is the file content identification used by Git when
>> +	the "text" attribute is "auto", or core.autocrlf != false.
>> ++
>> +"eolinfo" is either "" (when the the info is not available"), or one of "binary",
>> +"text-no-eol", "text-lf", "text-crlf" or "text-crlf-lf".
>
> <bikeshedding>
>
> Again, I think this list reads better as: binary, none, lf, crlf and mixed.
>
> If you prefer to have 'text' in there somewhere, how about:
>
>    binary, text-none, text-lf, text-crlf, text-mixed.
>
> :-D

Yup, these shorter ones, especially without "text-" prefix, read easier to humans; scripts won't mind either way, so I'd prefer that shorter version.

Thanks for reminding the thread.
Previous: Torsten BögershausenNext: Junio C Hamano
Message 4 of 5 in “ls-files: Add eol diagnostics”
  1. ls-files: Add eol diagnosticsTorsten Bögershausen, Dec 30, 2015
  2. Ramsay JonesDec 30, 2015
  3. Torsten BögershausenDec 30, 2015
  4. Junio C HamanoDec 30, 2015
  5. Junio C HamanoDec 30, 2015

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.