# Forcing CRLF for files in a directory

3 messages from 2010-07-01 to 2010-07-01. Participants: Ryan McCue, Eyvind Bernhardsen, Finn Arne Gangstad.
Thread: https://gitlist.dev/t/24252

## Ryan McCue, 2010-07-01 12:12

Subject: Forcing CRLF for files in a directory
Message-ID: <4C2C8644.4060208@ryanmccue.info>
URL: https://gitlist.dev/e/4C2C8644.4060208%40ryanmccue.info

```
Hi there,

I'm working on a project at the moment which stores raw HTTP header data 
along with bodies for use during testing. As each header line must be 
separated by a CRLF, these need to remain so in the repository.

My question is: Do I need to do anything special to ensure these CRLFs 
aren't converted to LFs during checkout?

Thanks,
Ryan.

```

## Eyvind Bernhardsen, 2010-07-01 13:37

Subject: Re: Forcing CRLF for files in a directory
Message-ID: <84784AAD-6276-4736-A04C-EDF55986C346@gmail.com>
URL: https://gitlist.dev/e/84784AAD-6276-4736-A04C-EDF55986C346%40gmail.com
In-Reply-To: <4C2C8644.4060208@ryanmccue.info>

```
On 1. juli 2010, at 14.12, Ryan McCue wrote:

> Hi there,
> 
> I'm working on a project at the moment which stores raw HTTP header data along with bodies for use during testing. As each header line must be separated by a CRLF, these need to remain so in the repository.
> 
> My question is: Do I need to do anything special to ensure these CRLFs aren't converted to LFs during checkout?

No.  As long as you don't set any attributes, git will by default leave your line endings alone on Linux.

You might get into trouble on Windows, because git defaults to converting line endings to CRLF on checkout (core.autocrlf=true) and gets confused when files are already checked in with CRLFs.  This problem is fixed in the upcoming 1.7.2 release.
-- 
Eyvind

```

## Finn Arne Gangstad, 2010-07-01 13:55

Subject: Re: Forcing CRLF for files in a directory
Message-ID: <20100701135500.GA20015@pvv.org>
URL: https://gitlist.dev/e/20100701135500.GA20015%40pvv.org
In-Reply-To: <4C2C8644.4060208@ryanmccue.info>

```
On Thu, Jul 01, 2010 at 10:12:52PM +1000, Ryan McCue wrote:
> Hi there,
>
> I'm working on a project at the moment which stores raw HTTP header data  
> along with bodies for use during testing. As each header line must be  
> separated by a CRLF, these need to remain so in the repository.
>
> My question is: Do I need to do anything special to ensure these CRLFs  
> aren't converted to LFs during checkout?

If you are working on Windows and have set autocrlf (default on in
msysgit), they will be converted to LF only in the repo if they are
auto-detected as text files, and will get LF when checked out on a
system with autocrlf false.

You can force autocrlf to not think of a file as a text file by
setting "-crlf" for that file in .gitattributes.

In the upcoming 1.7.2 release, autocrlf has been fixed to never
autodetect files with mixed line endings in the repository as text
files, but it will take considerable time before that version is used
everywhere I guess. Also, this won't really help you if you create the
files on Windows.

- Finn Arne

```