T
T
thehighhomie2017-02-07 20:41:09
git
thehighhomie, 2017-02-07 20:41:09

GIT: symbol differences?

I've been working on a git team for 3 months now, but I still couldn't figure out these warnings:
warning: LF will be replaced by CRLF in wp-includes/wlwmanifest.xml.
The file will have its original line endings in your working directory.
On English-language sites, I could not understand anything completely, English is not at that level, and the translator is not very helpful. But on Russian-language resources the situation is described differently, then this is nothing and not to pay attention (and my partner tells me so), then you need to climb into the abstruse settings of the git.
A request to experienced and knowledgeable people, explain if this needs to be fixed somehow or can I work without worrying about this?
Today I created a new repository, and uploaded a worpdress there for further development on it, and the same thing)) I'm just afraid that git will glue line feeds and carriage returns so that later I'll take my head)

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
Alexander Movchan, 2017-02-07
@thehighhomie

To indicate the end of the line (line endings), different operating systems use different character sets. So, in Unix-like systems, the line feed character ( LF ) is used, and in the Windows family of OS, a combination of two characters carriage return and line feed ( CRLF ).
Git uses the same way as unix systems by default, i.e. LF . But if you're on Windows, it will automatically convert CRLF to LF on commit, or vice versa on checkout.
PSA little wrong. Not sure if git will automatically convert by default. Therefore, if one of the developers uses Linux, and someone uses Windows, you may get in trouble. So it's better to make sure the core.autocrlf setting is enabled:
git config --global core.autocrlf true

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question