How does git deal with binary files?

问题:

• Do I have to set something to tell git if some files are binary, just like svn? Or, git just can handle binary data automatically?
• If I change the binary file, so that I have 100 binary revisions, will git just store all 100 versions individually in the repository?
• What are submodules for with git?

回答1:

1. Git can usually detect binary files automatically.
2. No, Git will attempt to store delta-based changesets if it's less expensive to (not always the case).
3. Submodules are used if you want to reference other Git repositories within your project.

回答2:

Git uses a heuristic to try to determine if a file is a binary. See this article for more information and how to force git to treat a given file as a binary.

For good tutorial on submodules see here and here.

回答3:

I had essentially the same problem: I wanted to git pickle files, which are binary, but git thinks they're text.

I found this chapter on Git Attributes in the Pro Git Book. So I resolved my issues by creating a .gitattributes file with this line:

*.pickle binary

回答4:

git add my-binary-file
git commit
git push

Will add your binary file; it is automatic.

Indeed, if you have 100 versions of your file it will store it (but compressed).

You can use submodules to make references to other repositories.

回答5:

The issue is with .gitignore

The following paths are ignored by one of your .gitignore files: XXX/YYYY/Bin1_0x1d_0x0d.bin

Use -f if you really want to add them.

git add -f XXX/YYYY/*

OR

git add -f XXX/YYYY/Bin1_0x1d_0x0d.bin