From: Sebastian Schuberth <sschuberth@gmail.com>
To: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] ls-files: Add eol diagnostics
Date: Sun, 1 Nov 2015 09:43:29 +0100 [thread overview]
Message-ID: <5635D0B1.9040800@gmail.com> (raw)
In-Reply-To: <vpqbnbfpc6p.fsf@anie.imag.fr>
On 31.10.2015 11:25, Matthieu Moy wrote:
>> ca:text-no-eol wt:text-no-eol t/t5100/empty
>> ca:binary wt:binary t/test-binary-2.png
>> ca:text-lf wt:text-lf t/t5100/rfc2047-info-0007
>> ca:text-lf wt:text-crlf doit.bat
>> ca:text-crlf-lf wt:text-crlf-lf locale/XX.po
>
> I would spell the first "in" or "idx" (for "index"), not "ca" (for
> "cache"). I think we avoid talking about "the cache" these days even
> though the doc sometimes says "cached in the index" (i.e. use "cache" as
> a verb, not a noun).
Good point, I'd prefer "idx" over ca", too.
However, the commit message says "to check if text files are stored normalized in the *repository*", yet the output refers to the index / cache. Is there a (potential) difference between line endings in the index and repo? AFAIK there is not. Any I find it a bit confusing to refer to the index where, as e.g. for a freshly cloned repo the index should be empty, yet you do have specific line endings in the repo.
Long story short, how about consistently talking about line endings in the repo, and also using "repo" instead of "ca" here?
--
Sebastian Schuberth
next prev parent reply other threads:[~2015-11-01 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 10:12 [PATCH v2] ls-files: Add eol diagnostics Torsten Bögershausen
2015-10-31 10:25 ` Matthieu Moy
2015-11-01 8:43 ` Sebastian Schuberth [this message]
2015-11-01 18:40 ` Matthieu Moy
2015-11-01 20:17 ` Sebastian Schuberth
2015-11-01 18:22 ` Junio C Hamano
2015-11-01 18:41 ` Matthieu Moy
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=5635D0B1.9040800@gmail.com \
--to=sschuberth@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--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 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.