16f6c0aecf
Inline adoc files when they are included exactly once. Also fix language tags because this inlining gives us better information on what language the code is written in.
38 lines
1.5 KiB
Plaintext
38 lines
1.5 KiB
Plaintext
== Why is this an issue?
|
|
|
|
All developers should use the same end-line character(s) to prevent polluting the history changelog of source files in the SCM engine. Moreover some SCM engines like Git might sometimes badly support use of Windows 'CRLF' end of line characters.
|
|
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
=== Message
|
|
|
|
Replace all non line feed end of line characters in this file "XXXX" by LF. (message at file level)
|
|
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
=== on 28 Sep 2014, 08:17:19 Evgeny Mandrikov wrote:
|
|
I'm removing C, {cpp} and Objective-C from targeted languages since this rule doesn't make sense for me, because:
|
|
|
|
* Windows users most likely will use CRLF, Linux - LF. That's exactly what we observe in C-Family world.
|
|
* Modern version control systems are able to transform code on-the-fly during extraction and commits from/to repository to match OS style of line endings. And Git isn't an exception. Moreover - in such case this rule will generate false-positives.
|
|
|
|
So what is the source to claim that Git has troubles?
|
|
|
|
|
|
Since origin of rule is PHP - if PHP interpreter has troubles with interpretation of line endings or if there is pitfalls in PHP language, then appropriate description should be done instead of current one.
|
|
|
|
Alternatively might be better to require consistent line endings of all source files.
|
|
|
|
=== on 6 Oct 2014, 19:15:08 Freddy Mallet wrote:
|
|
Same feeling, I've removed all languages from "Targeted languages" field.
|
|
|
|
endif::env-github,rspecator-view[]
|