Yeah, I was just wondering if there was a SVN-only trick to get that propset 
working.  Anyhow, this did the trick:

find . -name \*java -type f | xargs perl -pi -e 's/(\r\n|\n|\r)/\n/g'
find . -name \*java -type f | xargs svn propset svn:eol-style native

Otis
P.S.
Doron: I just happened to see ^Ms when editing one of the .java files with 
vi.:wq
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/  -  Tag  -  Search  -  Share

----- Original Message ----
From: Steven Parkes <[EMAIL PROTECTED]>
To: java-dev@lucene.apache.org
Sent: Monday, April 2, 2007 7:14:59 PM
Subject: RE: contrib/benchmark - DOS line endings

I think you need to make the files consistent first, something like
dos2unix or unix2dos should do this, if they're available on your
machine.

-----Original Message-----
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 02, 2007 3:47 PM
To: java-dev@lucene.apache.org
Subject: contrib/benchmark - DOS line endings

I noticed some contrib/benchmark files have DOS-style line endings.
Tried this, but failed:

$ svn propset svn:eol-style native
./src/java/org/apache/lucene/benchmark/byTask/tasks/SearchTravTask.java
subversion/libsvn_wc/props.c:1460: (apr_err=200009)
svn: File
'src/java/org/apache/lucene/benchmark/byTask/tasks/SearchTravTask.java'
has inconsistent newlines
subversion/libsvn_subr/subst.c:643: (apr_err=135000)
svn: Inconsistent line ending style


If anyone knows a SVN way of fixing this, I'm all eyes!

Otis
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/  -  Tag  -  Search  -  Share



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to