No; it won't corrupt them. It just (as expected) doesn't know how to diff
them nor does it try to. The problem would be if they were massive and if
they would change frequently (or sometimes more than once), which would
mean the amount of data you'd need to 'git clone' would grow much more
sharply than with non-binary files.
Consider games that have artists check in TIFFs that get processed during
build process. Or perhaps pre-baked .zip files containing all game artwork
for sake of faster game launch by developers. ("We don't need to build the
.zip, just the .exe.")
Neither really applies to us, unless we start going crazy with icons.
On Mon, May 25, 2015 at 4:09 PM, Fred Kiefer <fredkie...@gmx.de> wrote:
> Am 25.05.2015 um 16:57 schrieb Ivan Vučica:
> > You mention binary and large files -- how many binary and large files
> > do we stash? If it's "many", do we care enough to want to store them
> > in the main repository?
>
> What is the problem with binary files with git? Would our image files be
> affected? We have plenty of them in gui (tiff, gif, icns) and it would
> be great to know in advance that these wont get corrupted.
>
> _______________________________________________
> Gnustep-dev mailing list
> Gnustep-dev@gnu.org
> https://lists.gnu.org/mailman/listinfo/gnustep-dev
>
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
https://lists.gnu.org/mailman/listinfo/gnustep-dev
