RE: How to remove all the svn:eol-style native from the repository?

On Mon, 2006-10-09 at 16:13 +0200, Méresse Christophe wrote:

> > CVS would have been doing native eol conversion by default
> > for everything not marked binary. Normally that's what
> > you want at least in a cross platform environment (or one
> > that might ever be). If that was working for you under CVS,
> > why don't you want it under subversion?
> >
>
> Well, the fact is that with CVS, they were working on unix only
> but now that they have discovered TortoiseSVN, they often do
> their subversion operations on windows (throught samba) and
> work on unix. I know that may seem a bit strange...
> but anyway, that's like that. And that's why they don't want
> the versioning system to deal with the content of their files.

That's just bizarre. They want to check out files that won't
work under the OS where they do it??

> (They are not the first developers I encountered who have this
> point of view (that this should not be the versioning system job),
> and I must admit that they may be right, but that's a long debate... :) )

Given that text doesn't work unless converted for the native style
and developers tend to work with text, I don't really get that
concept. Wouldn't it be better to learn to use the native tools
(maybe eclipse/subeclipse) in the first place instead of building
something that will break when you do? If they want to work
under windows, I also expect them to want to edit there too.
Hasn't that come up?

> My advice is that it would be great if subversion could overload
> the svn:eol-style property in the client configuration (or/and in
> the command lines options), but that's an other story.

It would be great if text was portable. It isn't.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org