Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Can any dev look at the file ccmanager.h

<< < (2/2)

MortenMacFly:

--- Quote from: ollydbg on September 29, 2014, 02:52:11 am ---I have just commit the change. An idea way of setting EOL property is that we can set the EOL for all the .h and .cpp files in a folder, so that we don't need to set those EOL property for each single files. Not sure SVN can do this.  :)

--- End quote ---
I think you wouldn't want to handle EOL blindly for files in a folder probably even recursively. It makes me wonder that GIT allows you to do so... ???

ollydbg:

--- Quote from: MortenMacFly on September 29, 2014, 07:59:02 am ---
--- Quote from: ollydbg on September 29, 2014, 02:52:11 am ---I have just commit the change. An idea way of setting EOL property is that we can set the EOL for all the .h and .cpp files in a folder, so that we don't need to set those EOL property for each single files. Not sure SVN can do this.  :)

--- End quote ---
I think you wouldn't want to handle EOL blindly for files in a folder probably even recursively. It makes me wonder that GIT allows you to do so... ???

--- End quote ---
I'm not an git export, but it looks like git can set EOL depend on file extension, see:
gitattributes(5)

--- Quote ---End-of-line conversion

While git normally leaves file contents alone, it can be configured to normalize line endings to LF in the repository and, optionally, to convert them to CRLF when files are checked out.

Here is an example that will make git normalize .txt, .vcproj and .sh files, ensure that .vcproj files have CRLF and .sh files have LF in the working directory, and prevent .jpg files from being normalized regardless of their content.

*.txt           text
*.vcproj        eol=crlf
*.sh            eol=lf
*.jpg           -text


--- End quote ---

MortenMacFly:
Oh well yes, that makes sense.I thought it would be on a plain folder...

Navigation

[0] Message Index

[*] Previous page