cleaning up the EOL chaos in an existing repo

   i'm fairly sure i know the answer to this, but i want to make sure
there's no easier way. i've just been handed an existing source code
repo in which the source and header files are in a state of EOL chaos
-- some LF, some CRLF.

   since the repo is hosted on a linux system, i want to normalize
everything to stardard LF EOLs so, as i see it, the quickest and
dirtiest approach is to just "dos2unix" everything, then check it all
back in. it will make for a sizable commit, but i don't see any way
to avoid that. after which i can set properties on all of the source
files to make sure they stay that way.

   is that about right? thanks.

rday

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-12 18:06:06 CEST