Home/ Questions/Q 3306910
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T21:20:40+00:00

After a pull, git status tells me that I have changed a 16Mb xml

  • 0

After a pull, git status tells me that I have changed a 16Mb xml file.

I have not touched this file; but its possible that EOL issues cause git’s confusion (though I think not as I have autocrlf = input ).

Yet I write because I cannot get rid of this thing.

I have tried each of the following :

  1. git reset –hard HEAD
  2. git checkout — derived/workflow/xml/definitions.xml
  3. git stash save

After each of these, git status tells me :

# Changed but not updated:
#   (use "git add <file>..." to update what will be committed)
#   (use "git checkout -- <file>..." to discard changes in working directory)
#
#       modified:   derived/workflow/xml/definitions.xml

This is a problem because I can’t “stash pop” afterward, (even immediately after #3 above, after doing a ‘git stash save’)

Environment

  • Windows XP
  • Cygwin Git 1.7.1

Some questions

  • Is git failing silently due to this large file size? (Earlier I briefly saw git fail on a memory issue)
  • How do I work around this problem?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In this case, the problem stemmed from my “autocrlf” setting to “input”.

    For better or worse, our build process generated xml files with “CRLF” line endings.

    “git status” must work in conjunction with “autocrlf”. Though I had not touched or edited the file, “git status” must say “when you commit this file, git will have to modify it, so I will report it right-now as modified”.

    The “solution” was to turn off autocrlf.

    With no autocrlf, git status returned “the right thing”

    • 0