Binaries should not be kept in version control as they can be recreated. You should especially do with with Git, which is really bad at storing binaries.

>Problem is solved, probably with item 2 below.
>
>1) Since git uses the SHA-1 hash as key of a file, it can tell if it changes name. One author asked what defines a file, the name or the content?
>
>2) I want to keep in the repository all VFP binary files together with the text file created by FoxBin2Prg program, but I don't want git to attempt to merge the binary files. There is a way to do that explained here: https://medium.com/@porteneuve/how-to-make-git-preserve-specific-files-while-merging-18c92343826b#.25075jakz It uses a hook that git provides to call a procedure during merges (there are other hooks too). I created a VFP exe for that purpose, with which I intend to do further work.
>
>3) I also had several projects in separate directories that I wanted to consolidate in a single repository. These were variations of our main product which we normally merge by hand ( que horror! ). Since I mark all changes of a series with the same code, I wrote a program to import to a new branch all files of a file group (e.g. SCX / SCT / SC2 files) even if only one of them had the code of interest. Program available if anyone needs it. Merging branches with git is a separate step.
>
>In summary there is a lot to learn here, but well worth the effort.
>
>Thank you Fernando Bozzo and Linus Torvalds for these wonderful tools.
>
>Alex