Maybe this is something we can set in the repo with .gitattributes? https://help.github.com/articles/dealing-with-line-endings/#per-repository-settings. Seems to be a git thing, so maybe Apache infra will honor it too.
Barring that, I like the idea of catching it in lint and even documenting the crlf option on our developer's page. On Tue, Jun 7, 2016 at 1:14 AM, Allard Hoeve <allardho...@gmail.com> wrote: > Hey! > > I like UNIX-style endings because they are simpler. But then again, I'm not > on Windows anywhere. > > Did you know that you can append `?w=1` to any Github URL to ignore > white-space changes? > > Not really a solution, but it might help. > > Best, > > Allard > > On Tue, Jun 7, 2016 at 12:47 AM anthony shaw <anthonys...@apache.org> > wrote: > > > hello, > > > > I've noticed more recently that in PRs, people have AUTO_CLRF set to > > True in Git. this means that if they're developing in Linux, it will > > automatically change all the line endings in any files they commit and > > in Windows it will change them back. > > > > When you raise the PR, it looks, to the reviewer like the person > > changed all the lines, which is a minor issue. > > > > As far as Python is concerned, it doesn't care less. So this won't > > create any bugs, just annoying to review. > > > > You can configure pyLint to pick this up and throw an error, what does > > everyone think? > > >
