vcs: line endings after clone

Carbenium commented 6 years ago

Since b2fcbae8fb1fe857c36fdb6545532dbc7d78b79d git isn't happy with the line endings after a fresh clone.

> git status
On branch master
Your branch is up-to-date with 'origin/master'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

    modified:   help/es/es.po
    modified:   tests/data/amz/decrypted.amz
    modified:   tests/data/xspf/xspf-1_0.2.xsd

no changes added to commit (use "git add" and/or "git commit -a")

core.autocrlf is set to input.

arfbtwn commented 6 years ago

couple of the line ending settings in that commit may be wrong but I just tested with core.autocrlf set to input globally and it didn't occur on my system when I cloned. What's the output from git config -l?

Carbenium commented 6 years ago

Here you go:

core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true

arfbtwn commented 6 years ago

Odd, I retried with core.filemode set to true as I had that false but I still couldn't reproduce. What does git diff say about the difference, is it definitely line endings?

Carbenium commented 6 years ago

Well, just solved it by upgrading git from 2.7.4 to 2.14.2.

arfbtwn commented 6 years ago

Cool, mind if we close this one?

arfbtwn / banshee

vcs: line endings after clone #56