From: "Shane Sun via GitGitGadget" <gitgitgadget@gmail•com>
To: git@vger•kernel.org
Cc: Shane Sun <github@waterlemons2k•com>,
Shane Sun <github@waterlemons2k•com>
Subject: [PATCH] doc: fix case error of eol attribute in example
Date: Sun, 23 Jun 2024 21:40:17 +0000 [thread overview]
Message-ID: <pull.1736.git.git.1719178817386.gitgitgadget@gmail.com> (raw)
From: Shane Sun <github@waterlemons2k•com>
The eol attribute only accepts "crlf" and "lf",
but the example incorrectly capitalizes "crlf".
References:
- https://git-scm.com/docs/gitattributes#_eol
- https://github.com/git/git/blob/v2.45.2/convert.c#L1278
Signed-off-by: Shane Sun <github@waterlemons2k•com>
---
doc: fix case error of eol attribute in example
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1736%2FWaterLemons2k%2Ffix-case-error-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1736/WaterLemons2k/fix-case-error-v1
Pull-Request: https://github.com/git/git/pull/1736
Documentation/gitattributes.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt
index 80cae17f37d..e6150595af8 100644
--- a/Documentation/gitattributes.txt
+++ b/Documentation/gitattributes.txt
@@ -374,7 +374,7 @@ explicitly define the line endings with `eol` if the `working-tree-encoding`
attribute is used to avoid ambiguity.
------------------------
-*.ps1 text working-tree-encoding=UTF-16LE eol=CRLF
+*.ps1 text working-tree-encoding=UTF-16LE eol=crlf
------------------------
You can get a list of all available encodings on your platform with the
base-commit: 9005149a4a77e2d3409c6127bf4fd1a0893c3495
--
gitgitgadget
reply other threads:[~2024-06-23 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pull.1736.git.git.1719178817386.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=github@waterlemons2k$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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