Re: End-of-line style for the spec

I've changed the end-of-line to unix now.

I'm also going to merge in
https://github.com/WebAudio/web-audio-api/pull/807 soon, but according to
https://help.github.com/articles/dealing-with-line-endings/ this might
require some work when you check out the repo after PR #807 has landed.

I hope it isn't an issue, but
https://help.github.com/articles/dealing-with-line-endings/ tells you what
to do if you need to fix it. (But if you're lazy, I would consider just
cloning a new repo and manually creating and rebasing any branches you have
on the old repo to the new.  The git repo isn't that big.)

On Mon, May 9, 2016 at 10:28 AM, Raymond Toy <rtoy@google.com> wrote:

> I believe this is causing issues with current PRs (including the PR for
> issue #12).
>
> I'm going to fix the end-of-line issue now (forcing back to plain LF), and
> look into making git enforce this so that the developer can use his
> favorite line ending, but the repo uses just LF.
>
> On Thu, May 5, 2016 at 2:42 PM, Raymond Toy <rtoy@google.com> wrote:
>
>> While looking at doing some more small PRs for the spec, I noticed that
>> the spec suddenly now uses CR/LF for end-of-line (Windows style).
>> Previously, it was (I think) just LF (Unix style).
>>
>> Can we just choose one style and enforce it? (I think git can do this
>> automatically).  It's going to make merging pull requests a night-mare if
>> each pull request changes the end-of-line encoding.
>>
>> I prefer Unix because I edit the spec only on my linux or mac box and the
>> default style is LF.
>>
>> --
>> Ray
>>
>>
>>
>>
>