From: Adam Monsen <haircut@gmail.com>
To: git@vger.kernel.org
Subject: Re: .gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX
Date: Fri, 22 Jul 2011 08:56:27 -0500 [thread overview]
Message-ID: <4E29818B.40707@gmail.com> (raw)
In-Reply-To: <4E297C5C.8030104@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
I wrote:
> Anyone have ideas why my .gitattributes file isn't working?
drizzd on #git helped me out!
I went ahead and committed the file, and git replaced the line endings.
drizzd said the repository (the file object, I guess?) contained a file
with CRLF line endings, instead of LF line endings. But in my
checked-out version, I correctly see a file with CRLF line endings. Yay!
I generally follow the advice at http://help.github.com/line-endings/ in
terms of the core.autocrlf setting.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
prev parent reply other threads:[~2011-07-22 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 13:34 .gitattributes not forcing EOLs correctly for a CRLF-ending file on *NIX Adam Monsen
2011-07-22 13:56 ` Adam Monsen [this message]
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=4E29818B.40707@gmail.com \
--to=haircut@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;
as well as URLs for NNTP newsgroup(s).