From: Sebastian Schuberth <sschuberth@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: [PATCH v3] ls-files: Add eol diagnostics
Date: Sun, 22 Nov 2015 09:20:37 +0100 [thread overview]
Message-ID: <56517AD5.6040909@gmail.com> (raw)
In-Reply-To: <56501EFA.7050105@web.de>
On 21.11.2015 08:36, Torsten Bögershausen wrote:
> git ls-files --eol gives an output like this:
>
> i/text-no-eol w/text-no-eol attr/text=auto t/t5100/empty
I'm sorry if this has been discussed before, but hav you considered to use a header line and omit the prefixed from the columns instead? Like
index working tree attributes file
binary binary -text t/test-binary-2.png
text-lf text-lf eol=lf t/t5100/rfc2047-info-0007
text-lf text-crlf eol=crlf doit.bat
text-crlf-lf text-crlf-lf locale/XX.po
I believe this would be both easier to read for humans, and easier to parse for scripts that e.g. want to compare line endings in the index and working tree.
> +stats_ascii () {
> + case "$1" in
[...]
> + *)
> + echo huh $1
> + ;;
Personally, I'm not a big fan of supposedly funny output like this. How about printing a proper message rather than "huh", even for cases that should not happen?
--
Sebastian Schuberth
next prev parent reply other threads:[~2015-11-22 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 7:36 [PATCH v3] ls-files: Add eol diagnostics Torsten Bögershausen
2015-11-22 8:20 ` Sebastian Schuberth [this message]
2015-11-23 17:05 ` Torsten Bögershausen
2015-11-23 19:45 ` Sebastian Schuberth
2015-11-23 20:00 ` Eric Sunshine
2015-11-24 16:45 ` Ramsay Jones
2015-11-23 17:27 ` Eric Sunshine
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=56517AD5.6040909@gmail.com \
--to=sschuberth@gmail.com \
--cc=git@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).