diff options
| author | brian m. carlson <sandals@crustytoothpaste.net> | 2024-07-09 23:37:44 +0000 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-07-09 21:24:42 -0700 |
| commit | c98f78b806c93560c2a6c7eadda5449ac2a5432b (patch) | |
| tree | 5b0aad685ae97cffaa22a1c659cd7b9eb0f97825 /compat/regex/regcomp.c | |
| parent | 2101341484b093a7324ef8cd408af52c73cc5bea (diff) | |
gitfaq: give advice on using eol attribute in gitattributes
In the FAQ, we tell people how to use the text attribute, but we fail to
explain what to do with the eol attribute. As we ourselves have
noticed, most shell implementations do not care for carriage returns,
and as such, people will practically always want them to use LF endings.
Similar things can be said for batch files on Windows, except with CRLF
endings.
Since these are common things to have in a repository, let's help users
make a good decision by recommending that they use the gitattributes
file to correctly check out the endings.
In addition, let's correct the cross-reference to this question, which
originally referred to "the following entry", even though a new entry
has been inserted in between. The cross-reference notation should
prevent this from occurring and provide a link in formats, such as HTML,
which support that.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'compat/regex/regcomp.c')
0 files changed, 0 insertions, 0 deletions