Use `-text` git attribute instead of `text eol=...`

These automatic conversions lead to issues in various workflows, and all
we want here are files that retain their line endings under all
circumstances. `-text` captures that perfectly well and leads to fewer
issues.

It is preferable to `binary`, because with `-text` we still get textual
diffs.

Differential Revision: https://reviews.llvm.org/D124606
This commit is contained in:
Michael Forster 2022-04-28 12:54:49 +02:00
parent bbffece383
commit 4aba5fa774
3 changed files with 19 additions and 19 deletions

View File

@ -4,12 +4,12 @@
# These test input files rely on one-byte Unix (LF) line-endings, as they use
# fixed -offset, FileOffset:, or Offset: numbers in their tests.
clang-apply-replacements/ClangRenameClassReplacements.cpp text eol=lf
clang-apply-replacements/Inputs/basic/basic.h text eol=lf
clang-apply-replacements/Inputs/format/no.cpp text eol=lf
clang-apply-replacements/Inputs/format/yes.cpp text eol=lf
clang-tidy/infrastructure/export-diagnostics.cpp text eol=lf
clang-apply-replacements/ClangRenameClassReplacements.cpp -text
clang-apply-replacements/Inputs/basic/basic.h -text
clang-apply-replacements/Inputs/format/no.cpp -text
clang-apply-replacements/Inputs/format/yes.cpp -text
clang-tidy/infrastructure/export-diagnostics.cpp -text
# These test input files rely on two-byte Windows (CRLF) line endings.
clang-apply-replacements/Inputs/crlf/crlf.cpp text eol=crlf
clang-apply-replacements/Inputs/crlf/crlf.cpp.expected text eol=crlf
clang-apply-replacements/Inputs/crlf/crlf.cpp -text
clang-apply-replacements/Inputs/crlf/crlf.cpp.expected -text

View File

@ -1,6 +1,6 @@
// This file intentionally uses a CRLF newlines!
void foo() {
int *x = 0;
}
// This file intentionally uses a CRLF newlines!
void foo() {
int *x = 0;
}

View File

@ -1,6 +1,6 @@
// This file intentionally uses a CRLF newlines!
void foo() {
int *x = nullptr;
}
// This file intentionally uses a CRLF newlines!
void foo() {
int *x = nullptr;
}