- From: Rick Byers <rbyers@chromium.org>
- Date: Thu, 16 Apr 2015 20:13:47 -0400
- To: Daniel Freedman <dfreedm@google.com>
- Cc: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
- Message-ID: <CAFUtAY9Ebi=0aPaDM=2b_8RqbxtNV5_HT4Ewmh3MpTdgXZwgiA@mail.gmail.com>
Yeah, we can do that if necessary but I suspect the automatic settings are sufficient (since we just have a couple html and image files). I checked a handfull of other w3c repos and couldn't find a .gitattributes in any of them so didn't pursue that. On Thu, Apr 16, 2015 at 7:57 PM, Daniel Freedman <dfreedm@google.com> wrote: > Github suggests using a `.gitattributes` file to enforce platform > dependent line endings. > https://help.github.com/articles/dealing-with-line-endings/#per-repository-settings > > On Thu, Apr 16, 2015 at 3:17 PM, Rick Byers <rbyers@chromium.org> wrote: > >> Hey, >> I assume like for TECG we want one of the editors to approve pull >> requests, right? Looks like we don't yet have the automatic notification >> setup to IRC (or the list?). >> >> Before I make other changes, I think we should be normalizing line >> endings. Any objections? >> >> https://github.com/w3c/pointerevents/pull/5 >> The HTML files were checked into GitHub with CRLF line endings. GitHub >> (and Git generally) prefers the use of LF in the repo (see >> http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/ for a >> great detailed discussion). It should be easy for Windows users to have git >> auto-convert to CRLF (eg. "git config --global core.autocrlf true"), but >> it's apparently not easy for Linux/Mac users to have Git convert CRLFs in >> the repository to LF. I spot checked a few other W3C GitHub repos and the >> specs there all have LF line endings. >> >> This is the first non-trivial change in PEWG level 2, so hopefully >> diffing past it isn't a big deal. >> > >
Received on Friday, 17 April 2015 00:14:35 UTC