From: Raimund Bauer <ray007@gmx.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: autocrlf
Date: Fri, 18 May 2007 12:34:42 +0200 [thread overview]
Message-ID: <1179484482.6453.19.camel@localhost> (raw)
In-Reply-To: <200705181111.53823.andyparkins@gmail.com>
On Fri, 2007-05-18 at 11:11 +0100, Andy Parkins wrote:
> Hello,
>
> I've just been playing with gitattributes and was trying the crlf attribute.
> The behaviour of this and/or core.autocrlf is not as I was expecting.
>
> What I had imagined was that I could use .gitattributes to tell git which
> files in my tree were text. Then the line endings on checkout would be set
> as appropriate to my platform, and on check in set to LF.
>
> What actually happens is that any file with the crlf attribute is being
> checked out with LF expanded to CRLF (I'm running Linux of course), which is
> completely not what I wanted.
you need to set core.autoCrlf=input
I had the same problem some time ago ...
> Andy
--
best regards
Ray
next prev parent reply other threads:[~2007-05-18 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 10:11 autocrlf Andy Parkins
2007-05-18 10:34 ` Raimund Bauer [this message]
2007-05-18 12:01 ` autocrlf Andy Parkins
2007-05-18 11:45 ` autocrlf Johannes Sixt
2007-05-18 12:32 ` autocrlf Andy Parkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1179484482.6453.19.camel@localhost \
--to=ray007@gmx.net \
--cc=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox