-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We've hit this a couple times so it's probably worth making sure everyone's aware this is a bad idea and why. (don't think we've actually communicated this at any time)
In general git and svn both aren't so fond of binary data, they can't do diffs and thus any change to the file chews up a lot of storage. The situation with git is even worse because a git clone is a clone of the entire repository, all branches and history. Thus when we commit a huge binary file in git, even if we remove it later on, it's still included in all git checkouts and any future clones as well. (which is brutal for distant remotees or people with slow connections) So if you need to share a large binary file, we can keep our scm drastically more efficient if we find another way to host and share the file. Anyone have suggestions? Thanks, Devan - -- Devan Goodwin <dgood...@redhat.com> Software Engineer - Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklmPTkACgkQAyHWaPV9my7pOwCfVhKQ+JVkH8QFl0SgiCMWLY/N MPIAn1d8tj1G9IXfkni3pDNeJdVgq6LW =qIRf -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
