highperfocused/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-06-30 10:42:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge bitcoin/bitcoin#30010: lint: [doc] Clarify Windows line endings (CR LF) not to be used

Browse Source 
fa9be2f795 lint: [doc] Clarify Windows line endings (CR LF) not to be used (MarcoFalke)

Pull request description:

  It has been this case since the linter was introduced years ago. Given a misunderstanding (https://github.com/bitcoin/bitcoin/pull/28074#issuecomment-2088028856), clarify the docs.

ACKs for top commit:
  brunoerg:
    ACK fa9be2f795

Tree-SHA512: be714db9df533e0962ed84102ffdb72717902949b930d58cf5a79cba36297f6b2b1f75e65a2c1f46bcb8e2f4ad5d025f3d15210f468a5ec9631a580b74f923ea
This commit is contained in:
merge-script
2024-05-02 11:45:23 +08:00
parent 1cc3aa4d21 fa9be2f795
commit 59b773f42a
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
test/lint/test_runner/src/main.rs
View File

@ -137,9 +137,9 @@ fn lint_trailing_whitespace() -> LintResult {
if trailing_space { if trailing_space {
Err(r#" Err(r#"
^^^ ^^^
Trailing whitespace is problematic, because git may warn about it, or editors may remove it by Trailing whitespace (including Windows line endings [CR LF]) is problematic, because git may warn
default, forcing developers in the future to either undo the changes manually or spend time on about it, or editors may remove it by default, forcing developers in the future to either undo the
review. changes manually or spend time on review.
Thus, it is best to remove the trailing space now. Thus, it is best to remove the trailing space now.