342894 - examples/E4X/e4x_example.js has line endings inconsistent with rest of source tree

Status: RESOLVED FIXED

(Rhino Graveyard :: E4X, defect)

Description

[David Caldwell]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Rhino HEAD 27-Jun-2006 3:03PM EDT

Yes, it's not a big deal, but it adds an extra step to building patches (or causes me to exclude this file altogether) and it would be easy to fix for someone with commit privileges, so I'm putting it into the system in the hopes that someone has a few minutes ...

Reproducible: Always

Steps to Reproduce:
1.  Check out mozilla/js/rhino/examples/E4X/e4x_example.js

Actual Results:  
Has CR/LF line endings

Expected Results:  
LF line endings like every other file in the tree

It would make it easier to build patches against the tree without preprocessing the file or excluding it from the patch, which would be nice for people who don't have time to write command-line scripts to do that stuff.

Comment 1

[David Caldwell]

Attachment: Version with LF instead of CR/LF line endings

Comment 2

[Attila Szegedi]

Committed, thanks for submitting it.