Nicklas Norling wrote:
>> -----Original Message-----
>> From: Max Bowsher [mailto:firstname.lastname@example.org]
>> The fact that you *have* to set eol-style to get eol
>> translation is a deliberate design decision, due to the fact
>> that a common complaint of Windows CVS users is "I checked in
>> an image and it was corrupted" - because CVS eol-converted
>> it. So subversion does things the other way around, and makes
>> you say, "yes, I really do want this file eol-converted."
> I'd say most windows CVS users use TCVS as it has such a compelling
> UI and windows users tends to like that. I have not had any problem
> with checking in files where TCVS did not figure out the correct
> eol style. If a file ending is unknown it will ask me.
> In my mind the design is taking a pretty rare case into account too
> much. The result is that a conversion from cvs to subversion using
> cvs2svn creates a repository that is not able to create a correct
> wc on a windows machine per default.
> Also one should take into account the horrid task to add svn:eol-style
> to each and every text file in the converted repository. I know that
> that is less of a hassle on a *nix machine where find grep etc. and
> in existence, but in windows all I have is TSVN to manually change the
> tens of thousands of files, making sure I only change the text based.
> I'm about to convert our production cvs within days, I would have
> hoped to be able to do this without svn:eol-style.
> Is there any workarounds other then manually editing these files?
> If I was able to setup a *nix machine, could I somehow do this more
> automatically? Getting desperate here...
>> Further discussion on svn:eol-style should be directed to
>> users@subversion, not users@cvs2svn.
Regarding operation of svn:eol-style after conversion, look in the svnbook
Regarding automatic setting of svn:eol-style during cvs2svn conversion,
there is a pending patch by Stefan Haller, which will probably be integrated
some time this weekend.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Mar 26 11:44:45 2004