From: Junio C Hamano <gitster@pobox•com>
To: Alexandre Garnier <zigarn@gmail•com>
Cc: "Torsten Bögershausen" <tboegi@web•de>, git@vger•kernel.org
Subject: Re: [BUG] Git does not convert CRLF=>LF on files with \r not before \n
Date: Wed, 22 Apr 2015 10:42:53 -0700 [thread overview]
Message-ID: <xmqq618of49u.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAFFOgCVkpweSukCW4La737P1uu1hqX8WKr9wF1cLV8ciPu8tuQ@mail.gmail.com> (Alexandre Garnier's message of "Wed, 22 Apr 2015 15:06:38 +0200")
Alexandre Garnier <zigarn@gmail•com> writes:
> Indeed, when changing the gitattributes for '* text', the replacement is OK.
OK. Earlier I said:
>> But it would be a bug if the same thing happens when the user
>> explicitly tells us that the file has CRLF line endings, and I
>> suspect we have that bug, which may want to be corrected.
but you are saying that my suspicion is incorrect and we do not have
such a bug.
Thanks for digging further.
prev parent reply other threads:[~2015-04-22 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 13:51 [BUG] Git does not convert CRLF=>LF on files with \r not before \n Alexandre Garnier
2015-04-21 17:41 ` Junio C Hamano
2015-04-21 19:28 ` Torsten Bögershausen
2015-04-22 13:06 ` Alexandre Garnier
2015-04-22 17:42 ` Junio C Hamano [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=xmqq618of49u.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=tboegi@web$(echo .)de \
--cc=zigarn@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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