Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing typo in README #5

Merged
merged 1 commit into from
Mar 18, 2015
Merged

Fixing typo in README #5

merged 1 commit into from
Mar 18, 2015

Conversation

claylevering
Copy link
Contributor

Just fixed the yml -> yaml typo in the example code 👍

@rtluckie
Copy link
Owner

@claylevering Welcome and thanks for the pull request! Gonna merge this PR, but I wanted to ask your opinion on yaml vs yml extension. YAML faqs ask that users "Please use '.yaml' when possible.", but I have come across several implementations that ignore this request (travis) and require the yml extension.
This is a completely immaterial question, but I just like hearing other's opinions on such matters. 😏

rtluckie added a commit that referenced this pull request Mar 18, 2015
Fixing typo in README.

Maybe we should allow yml as output format in CLI.
@rtluckie rtluckie merged commit 5def60b into rtluckie:master Mar 18, 2015
@claylevering
Copy link
Contributor Author

I feel like this is a difference between 'file format' and 'name' and an inevitable consequence of old-school 8.3 Windows users. I think of 'mpeg' vs 'mpg'. It only becomes complicated, in my opinion, when the full-name comes dangerously close to three letters and could therefore also become an extension. You don't ever see an MKV file with a .Matroska extension.

Also, I figure if Travis ignores it, that's a fairly solid ground for dismissal of the 'rule'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants