From: Raimund Bauer <ray007@gmx.net>
To: git <git@vger.kernel.org>
Subject: Problems with autoCRLF?
Date: Fri, 09 Mar 2007 19:15:02 +0100 [thread overview]
Message-ID: <1173464102.6102.18.camel@localhost> (raw)
Is it really intended that with a setting core.autoCRLF=true textfiles
are checked out with crlf-lineendings on linux-boxes?
I found out because the git-compilation broke ...
Now using core.autocrlf=input ;-)
--
best regards
Ray
next reply other threads:[~2007-03-09 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 18:15 Raimund Bauer [this message]
2007-03-09 19:51 ` Problems with autoCRLF? Robin Rosenberg
2007-03-09 21:38 ` Linus Torvalds
2007-03-10 1:24 ` Junio C Hamano
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=1173464102.6102.18.camel@localhost \
--to=ray007@gmx.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.