From: Dmitry Potapov <dpotapov@gmail.com>
To: Robert Buck <buck.robert.j@gmail.com>
Cc: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>,
"git@vger.kernel.org List" <git@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
mat <matthieu.stigler@gmail.com>,
hasen j <hasan.aljudy@gmail.com>,
Erik Faye-Lund <kusmabite@googlemail.com>,
Junio C Hamano <gitster@pobox.com>,
Avery Pennarun <apenwarr@gmail.com>,
Finn Arne Gangstad <finnag@pvv.org>
Subject: Re: [PATCH/RFC v2 1/4] Add "core.eolStyle" variable to control end-of-line conversion
Date: Mon, 10 May 2010 18:03:21 +0400 [thread overview]
Message-ID: <20100510140321.GF14069@dpotapov.dyndns.org> (raw)
In-Reply-To: <AANLkTikYUypxH5WhCOMby_zpHsnHEFyix5MGpD96FVWD@mail.gmail.com>
On Mon, May 10, 2010 at 09:25:11AM -0400, Robert Buck wrote:
> Today I am writing up some documentation related to Git use at the
> company, and planning to check in all the data from Git vs Hg testing,
> and all on-boarding/first-day documentation related to Git use. So
> within the directory containing all these files I init-ed the
> repository and got this when I attempted to add multiple files. Mind
> you, this is on Linux!
>
> "warning: LF will be replaced by CRLF"
It looks like you set core.autocrlf to true on Linux.
The problem is core.autocrlf says two things -- whether you want to
enable automatic eol conversion for text files and whether you have CRLF
for text files. Only if the answer is "yes" to both then you should set
it to true. In other words, you should never set it to true on Linux.
You may want use core.autocrlf=input on Linux to avoid text files being
accidentally commit with a wrong encoding, when they were copied from
Windows directly.
>
> This _really_ of scares me being that this was on Linux. Is this one
> of the problem spots that the topic of this thread attempts to
> resolve?
Yes, we want to have a separate setting, whihc will tell what is EOL on
your system, and it should have sensible default, i.e. LF on Linux and
CRLF on Windows.
Dmitry
next prev parent reply other threads:[~2010-05-10 14:03 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 21:46 [PATCH/RFC v2 0/4] End-of-line normalization, take 2 (now only slightly scary) Eyvind Bernhardsen
2010-05-08 21:46 ` [PATCH/RFC v2 1/4] Add "core.eolStyle" variable to control end-of-line conversion Eyvind Bernhardsen
2010-05-08 21:57 ` Linus Torvalds
2010-05-08 22:17 ` Eyvind Bernhardsen
2010-05-08 22:53 ` Eyvind Bernhardsen
2010-05-08 23:08 ` Linus Torvalds
2010-05-09 8:13 ` Eyvind Bernhardsen
2010-05-09 18:11 ` Linus Torvalds
2010-05-09 20:11 ` Eyvind Bernhardsen
2010-05-09 7:00 ` Dmitry Potapov
2010-05-09 7:30 ` hasen j
2010-05-10 7:16 ` Dmitry Potapov
2010-05-09 8:34 ` Eyvind Bernhardsen
2010-05-09 10:42 ` Eyvind Bernhardsen
2010-05-09 11:14 ` Robert Buck
2010-05-09 18:59 ` Eyvind Bernhardsen
2010-05-09 20:46 ` Robert Buck
2010-05-10 4:33 ` Eyvind Bernhardsen
2010-05-10 11:43 ` Robert Buck
2010-05-10 13:25 ` Robert Buck
2010-05-10 14:03 ` Dmitry Potapov [this message]
2010-05-09 17:02 ` Jay Soffian
2010-05-09 17:43 ` Jay Soffian
2010-05-10 18:33 ` Eyvind Bernhardsen
2010-05-09 17:45 ` Junio C Hamano
2010-05-09 18:18 ` Finn Arne Gangstad
2010-05-09 21:57 ` Junio C Hamano
2010-05-10 5:14 ` Eyvind Bernhardsen
2010-05-09 20:25 ` Eyvind Bernhardsen
2010-05-09 20:09 ` Finn Arne Gangstad
2010-05-10 8:13 ` Dmitry Potapov
2010-05-10 11:14 ` Finn Arne Gangstad
2010-05-10 13:46 ` Dmitry Potapov
2010-05-09 9:21 ` Finn Arne Gangstad
2010-05-08 21:46 ` [PATCH/RFC v2 2/4] Add tests for per-repository eol normalization Eyvind Bernhardsen
2010-05-08 21:46 ` [PATCH/RFC v2 3/4] Pass eol conv mode as an argument instead of using global auto_crlf Eyvind Bernhardsen
2010-05-08 21:46 ` [PATCH/RFC v2 4/4] Add per-repository eol normalization Eyvind Bernhardsen
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=20100510140321.GF14069@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=apenwarr@gmail.com \
--cc=buck.robert.j@gmail.com \
--cc=eyvind.bernhardsen@gmail.com \
--cc=finnag@pvv.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hasan.aljudy@gmail.com \
--cc=kusmabite@googlemail.com \
--cc=matthieu.stigler@gmail.com \
--cc=torvalds@linux-foundation.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).