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

Re: doing a massive EOL normalization for a small group of users?

From: Robert P. J. Day <rpjday_at_crashcourse.ca>
Date: Wed, 29 Oct 2008 14:38:14 -0400

Quoting David Weintraub <qazwart_at_gmail.com>:

> As far as I can see, you'll have to do this and this will interrupt
> everyone who is currently editing.
> First off, add a pre-commit hook that will fail a commit if a file
> being edited is of the right type and doesn't have the required
> svn:eol-style property set to the correct value. I don't know if the
> current Python pre-commit hook can do this, but I have a Perl
> pre-commit hook that does this type of checking as well as folder
> permission checking. Let me know if you want a copy of it.

   sure, send it along, but for the moment, i'm going to hold off
on that as my first priority is to just get the normalization done
and get everything sync'ed. once that's done, i can add the properties
and commit hooks at my leisure to keep everything that way.

> After that, you'll have to do a massive checkout that will checkout
> the entire repository, and add the svn:eol-style property to the file,
> then do a checkin. This of course, has to be coordinated with
> everyone. Some people will be editing these same files, and will get a
> commit conflict when they attempt to check them in. But, it isn't all
> that bad. You're not modifying the file, only the property. The merge,
> although a pain (I hate it when commits fail too) is pretty simple.

   again, adding that property is something that can be done afterwards
to keep things clean once they've been cleaned up. my number one
priority is to just get there, so i'm about to give it a shot. i'm
still curious if anyone's ever actually *done* this, and the exact
order of the steps to make it go smoothly, including what to get
the users to do in preparation, assuming that they simply can't
drop everything they're doing and check in all their changes.


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-29 19:38:39 CET

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.