Re: git-archive and core.eol
- From
Erik Faye-Lund <kusmabite@gmail.com>
- Date
- Jan 10, 2011, 13:00 UTC
- Message-ID
- <AANLkTi=WyzVzPkhOAMC2A8Dd=Zj_P-7YMVP-GaUz0-Qm@mail.gmail.com>
- In-Reply-To
- <AANLkTinxVCQuTMeKHQ9mLbs=94fck90rwJwa1DhzGPmX@mail.gmail.com>
On Mon, Jan 10, 2011 at 1:11 PM, Erik Faye-Lund <kusmabite@gmail.com> wrote:
> test. So now I've got to figure out what is different between your > test and mine. Perhaps I misdiagnosed to begin with? >
No, it doesn't quite seem like I misdiagnosed, but your test had different expectations than I have after reading the documentation. I expected core.autocrlf=true + core.eol=lf to pretty much be identical to core.autocrlf=false, but only because LF->LF conversion is a NOP.
'core.autocrlf' is documented as meaning the same as setting the 'text' attribute to 'auto' for all files, plus "files that contain CRLF in the repository will not be touched". I figured that last part shouldn't affect me as I only had LFs in the repository.
If I disable core.autocrlf, I get what I want (no matter what I set core.eol to, it seems). But I still don't understand WHY core.autocrlf=true + core.eol=lf outputs CRLF.
It seems to me that there's a big gap between what the documentation claims and what actually happens here.