Re: Checking in files with trailing white space

[Eli Zaretskii]

> From: Paul Eggert <address@hidden>
> Date: Wed, 14 Dec 2016 10:15:55 -0800
> Cc: address@hidden, address@hidden, address@hidden
> 
> I've attached a list of repository-controlled files that are not UTF-8 
> text files in the POSIX sense. Of the 433 such files, I count 181 Netpbm 
> image data, 107 gzipped files (mostly gzipped text), 57 PNG files, 11 
> PDF files, and there is a hodgepodge of assorted other formats. A few 
> files are in the list merely because they lack a trailing newline (a 
> problem for some tools, and POSIX says such files are not text files). 
> (For a sense of the scale here, all this is out of 3695 files total in 
> Emacs master right now.)
> 
> Most of the files in this list are merely awkward and are not a GPL 
> issue; these include the gzipped text files, the text files that use 
> non-UTF-8 encodings, and the no-trailing-newline files. And many files 
> are there because we have put object files into the source repository, 
> where we really should be generate them as part of the build and limit 
> the repository to source code; these include the PBM and PNG files (or 
> at least I hope they do; I haven't checked).

There are no licensing issues with any of those, each one was verified
at the time, AFAIR.

As for generating them from text: feel free to scratch that itch, if
you want to.

> > Depends on the compression method, I guess. For some of them, we
> > cannot rely on the respective tools being available, so if that
> > particular kind of compression is needed for some test, having the
> > source file might not be good enough.
> 
> We can assume gzip

Yes.  Gzip was not what I had in mind.