All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: [PATCH v8] ls-files: Add eol diagnostics
Date: Wed, 30 Dec 2015 13:45:42 -0800	[thread overview]
Message-ID: <xmqqsi2jd309.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <5683E8B4.7040005@ramsayjones.plus.com> (Ramsay Jones's message of "Wed, 30 Dec 2015 14:22:44 +0000")

Ramsay Jones <ramsay@ramsayjones.plus.com> writes:

>> +	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.

  parent reply	other threads:[~2015-12-30 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 12:57 [PATCH v8] ls-files: Add eol diagnostics Torsten Bögershausen
2015-12-30 14:22 ` Ramsay Jones
2015-12-30 15:27   ` Torsten Bögershausen
2015-12-30 21:45   ` Junio C Hamano [this message]
2015-12-30 21:43 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqsi2jd309.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=tboegi@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.