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

Fwd: Re: cleaning up the EOL chaos in an existing repo

From: Robert P. J. Day <rpjday_at_crashcourse.ca>
Date: Fri, 12 Sep 2008 12:44:30 -0400

(Sorry, I should have replied to the list, not just to David.)

Quoting David Weintraub <qazwart_at_gmail.com>:

> That's probably all you can do once the repository is already in
> Subversion. BTW, if you do that, put the svn:eol-style property on
> when you do a clean up, so you don't have to commit everything twice.

ah, quite right ... adding all those properties later would provoke
another massive commit. good point.

> Another thought: Do an 'svnadmin dump', filter it, then do a "svnadmin
> load". The dump format is pretty simple, and shouldn't be hard to
> write a Python or Perl script to do the cleanup (and add the
> svn:eol-style property while it's at it.)

hmmmm ... i'll give that some thought, it sounds suitably challenging.

> Yet, another thought: Don't do anything. Instead, just make a
> pre-commit hook that requires the svn:eol-style property be set on
> particular files (with a particular value). As people make changes,
> they'll have to add the svn:eol-style property to do the cleanup. When
> the file gets committed, it will be checked in with the correct line
> ending.

i'd thought of that, but i want to be able to edit arbitrary files
in my working copy without being faced with countless ^M's all the
time, so i'd rather just deal with this once and for all.


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:44:53 CEST

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.