On Thu, Feb 13, 2014 at 10:30 AM, Kent Fredric <kentfred...@gmail.com> wrote: > > On 14 February 2014 04:28, Anthony G. Basile <bluen...@gentoo.org> wrote: >> >> 2) You want your vcs to show the diff in that file and you can make sense >> of that diff. > > > Though how many of them are "well formatted" SVGs, and how many of them are > single-line SVG files without whitespace, such as linefeeds and appropriate > indentation? > > Because diffs are usually not very useful if lots of changes occur on a > single line.
If these were really hand-maintained SVG files I could see how it might fit into an scm model. However, these are text files in the same sense that an assembly language listing generated from a C++ file would be. Sure, you could manipulate it by hand, but the reality is that upstream is going to change 47 lines in the source and you're going to upgrade your gcc and as a result 90% of the 3M line listing will change on a small upgrade. Likewise, when upsteam changes their desktop icon it isn't going to result in a 3-line change to the SVG file. I guess the question though is whether they cause harm. If the files are small and don't cause issues with the scm they're stored in, then I don't really see the issue with storing them. It doesn't really matter if they're SVG files or uuencoded whatever (though if our tree is GPL we need to make source available for anything that has it - probably not an issue for SVG unless it is derived from some kind of composite). Rich
