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

RE: how to?

From: Jack Repenning <jrepenning_at_collab.net>
Date: 2003-05-15 22:53:11 CEST

> is an additional option to "svn up" a possibility, like "svn up
> --eol-style=unix"?
> or is it the best thing to just run "find ... -exec perl -i -pe
> 's/^M//g' {}" on the whole tree?

There are files that should not have their content translated, even if
it does happen to look like a ^M. Maybe there aren't any in your tree
(if you only have source code, that's likely), but you can start with
"anything binary." That seems to rule out the "find/perl" trick.

The switch to "svn up" is interesting, so long as it only affects
handling of things with svn:eol-style=native. Might be better if its
name had 'native' in it, or 'platform' ... "--eol-style-platform=unix",

If there were such a switch, I think it should be cached so that the

        svn up --eol-style-platform=unix
        svn up

Would get unix line endings both times; if you change your mind, you'd
need an explicit reuse of --eol-style-platform.

And that means it needs a "return to normal processing" value, in
addition to the explicit possibilities. Or, maybe that's "native".

And it should be cached on a per-file basis.

And this is getting pretty complicated....

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 15 22:54:01 2003

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

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