Keep in mind there's another important situation that you can't control it like this.
According to the ASF the -sources.zip are the official release, not the git tag. This means that you should unpack the zip and be able to verify it on all OSes. In this case you don't control the EOL, it is based on the OS of the release manager. The only way to solve this is to generate files on the fly, or adjust them before testing. You won't see this issue with the CI server, only after a release and when verified with different OSes. thanks, Robert On 18-7-2019 14:49:02, Eric Lilja <mindcoo...@gmail.com> wrote: Ah, thanks Vladimir, that's even better. I was not 100% sure it would be possible to retain complete control over resulting line endings for those files, regardless of user git settings of stuff like autocrlf = true and whatnot, but it seems there is, that's great news. Thanks! - Eric L On Thu, Jul 18, 2019 at 2:00 PM Vladimir Sitnikov <> sitnikov.vladi...@gmail.com> wrote: > Eric>In that case, we should generate the test files (to > Eric>avoid git interfering), one with linux-style EOLs and one with > Eric>Windows-style EOLs and test with both. > > You'd better have those files under Git control, and you could just specify > .gitattributes so the LF file is always LF, and CRLF file is always CRLF. > > That is way simpler than generation of the file(s), and it is way easier to > understand by humans > > Vladimir >
