I've noticed, that (except of only a very few) nearly all SVG files are committed as SVGZ to our git repositories.
This has IMHO several drawbacks: - every change will be stored as a single atomic blob - git's internal packfile compression and deduplication can't be used - no diffs for changes done to SVGs can be viewed - batch-editing of files via sed/awk/… is way more difficult I'd like to suggest to implement a git hook which enforces SVG files being pushed uncompressed. The compression of SVG to SVGZ might happen when building release tarballs. What are your thoughts? Any reasons not to do this? - Elias P.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
