[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: eol-style

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-06-01 15:04:47 CEST

> From: Russ Brown [mailto:pickscrape@gmail.com]
> What I'm looking for is a way to correct the whole lot and commit the
> fix in one big changeset. That will result in loads of conflicts in
> the next few branch merges, but would fix the problem once and for all
> going forward. The question is, how to do that. svn doesn't want to
> commit the file unless the file gets changed, so I suspect that I'd
> have to change the files in some way (though that is hardly ideal).
> Anything else I can try?

You could probably do something like this: Make a complete checkout. Use
"svn propget -R svn:eol-style" to list all the files that have svn:eol-style
set, and the values. Save that list. Do "svn propdel -R svn:eol-style" to
remove all the eol-styles. At this point your WC is OK. Now massage that
list you made into a set of "svn propset svn:eol-style <value> <file>"
commands and execute them. In the background, your client will edit the
EOLs on the files to make them consistent with the eol-styles you set, or at
least flag them as incorrect, which you can fix by hand or script. Now
check the mess in. That should make your repository consistent.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 1 15:07:50 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.