From: "Alexander Veit" <alexander.veit@gmx.net>
To: <git@vger.kernel.org>
Subject: Re: Per file configurable eol-style transformations with Git?
Date: Sun, 22 Nov 2009 00:49:57 +0100 [thread overview]
Message-ID: <1050CAACABF64864A0CF79C957BF773B@helium> (raw)
In-Reply-To: <m3tywnbmpj.fsf@localhost.localdomain>
Jakub Narebski wrote:
> See `crlf` attribute, which can be set, unset, unspecified, set
> to "input", and used together with core.autocrlf ("true", "false",
> "input") and core.safecrlf. Attributes can be set per path (using
> globbing patterns) in .gitattributes file in tree, or in
> .git/info/attributes (per repository).
I've already tried
[core]
autoCRLF = true
in the global gitconfig under Windows. After git clone an immediate
git diff shows every line changed in certain files:
diff --git a/c_crlf_text.txt b/c_crlf_text.txt
index 3b0a76f..3473745 100644
--- a/c_crlf_text.txt
+++ b/c_crlf_text.txt
@@ -1,5 +1,5 @@
-z1
-z2
-z3
-z4
-
+z1
+z2
+z3
+z4
+
file * on Windows:
c___lf_text.txt; ASCII text, with CRLF line terminators
c_crlf_text.txt; ASCII text, with CRLF line terminators
file * on Linux
c_crlf_text.txt: ASCII text, with CRLF line terminators
c___lf_text.txt: ASCII text
I don't know if this behaviour is supposed to be correct,
but to me it seems to be wrong.
git version 1.6.5.1.1367.gcd48
--
Cheers,
Alex
next prev parent reply other threads:[~2009-11-21 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 20:21 Per file configurable eol-style transformations with Git? Alexander Veit
2009-11-21 21:18 ` Jakub Narebski
2009-11-21 23:49 ` Alexander Veit [this message]
2009-11-22 1:24 ` Junio C Hamano
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=1050CAACABF64864A0CF79C957BF773B@helium \
--to=alexander.veit@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox