From: Junio C Hamano <junkio@cox.net>
To: Raimund Bauer <ray007@gmx.net>
Cc: git <git@vger.kernel.org>
Subject: Re: Problems with autoCRLF?
Date: Fri, 09 Mar 2007 17:24:35 -0800 [thread overview]
Message-ID: <7v8xe528mk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1173464102.6102.18.camel@localhost> (Raimund Bauer's message of "Fri, 09 Mar 2007 19:15:02 +0100")
Raimund Bauer <ray007@gmx.net> writes:
> Is it really intended that with a setting core.autoCRLF=true textfiles
> are checked out with crlf-lineendings on linux-boxes?
Yes. The implicit assumption with any setting to core.autoCRLF
is that you want to keep the git objects free of CRLF line
endings.
- core.autoCRLF 'true' means that your tools that handle text
files would be upset findign LF line endings, and they will
leave text in CRLF line endings. Checking out from git
creates working tree files while adding CR before LF as
needed, and checking in from working tree files to git strips
CR before LF as needed.
- core.autoCRLF 'input' means that your tools do not mind
handling text files in LF line endings and they will leave
text in CRLF line endings, so checking out from git creates
working tree files by just giving what is stored in the
repository, and checking in from working tree files to git
strips CR before LF as needed.
So on sane platforms, you do not want to set that variable,
unless you are helping to test and improve that feature.
next prev parent reply other threads:[~2007-03-10 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 18:15 Problems with autoCRLF? Raimund Bauer
2007-03-09 19:51 ` Robin Rosenberg
2007-03-09 21:38 ` Linus Torvalds
2007-03-10 1:24 ` Junio C Hamano [this message]
2007-03-10 12:23 ` Raimund Bauer
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=7v8xe528mk.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=ray007@gmx.net \
/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).