Feature Wish

[Ralf Wiebicke <ra...@rw7.de>]

Hi there!

I recently made a disturbing experience with CVS. I hope SVN will do better 
once it's released, so I'll describe the problem.

I was a newbie on CVS. I already dealt with the issue of different line 
breaks on different systems. So I was glad to read, that CVS will handle this 
automagically. However, I managed to get DOS line breaks into the repository.

All I did was using a UNIX CVS client to import text files with DOS line 
breaks. The UNIX client doesn't check for UNIX line breaks, it just assumes 
that they are there. 

For the UNIX client, the 0D is just a character on the line. If another unix 
client checks out, it gets correct DOS text files. However, I a DOS client 
checks out these files, the 0D0A becomes 0D0D0A. Some editors treat this as 
two line breaks, which messes up the whole text file.

To make the trouble complete, CVS somehow managed to add a single UNIX line 
break at the end of each file. Thus, the files where mixed line break 
flavour, which causes GNU recode to refuse the dos2unix translation (no 
--force switch there). I finally used zip/unzip to do the conversion.

Please !!!, make subversion better.

Regards,
Ralf Wiebicke.

PS: I'm not subscribed to this list. If there are any comments, which I 
should know, please send me a copy.



-- 
Ralf Wiebicke <ra...@rw7.de>
http://rw7.de/ralf/

Re: Feature Wish

[Ralf Wiebicke <ra...@rw7.de>]

Am Thu, 12 Oct 2000 schrieben Sie:

> Well, sed 's/^M//' should be just OK instead of recode.
> it won't complain. :)
Is there anything, that sed cant do? :-)

> anyway, I really wouldn't like SVN to try and outsmart me..
> if I have 0x0d in my unix files, I probly put them there
> for a reason, so my vote is a definite no for your wish if
My reason was, that I overttook maintance of a existing java project. The 
former maintainer used WinXX, while I use Linux.  The first thing I did was 
introducing this CVS thing, to avoid the version trouble experienced until 
then.

> it should be the default behavior.  If there is a
> --be-smart-about-0x0d switch to do this,  then I have no
> objection, though.
Better think about the newbie. I think, SVN should find out, that it's a DOS 
file and offer a) to convert it to unix or b) treat it as binary or c) take 
it as is. Switches could be --treat-DOS-text-as-binary and 
--convert-DOS-to-unix etc. The default should always be to ask the user.

Ralf.


-- 
Ralf Wiebicke <ra...@rw7.de>
http://rw7.de/ralf/

Re: Feature Wish

[RADICS Peter <mi...@freemail.hu>]

Ralf Wiebicke <ra...@rw7.de> írta:

[SNIP] 
> To make the trouble complete, CVS somehow managed to add a
single UNIX line 
> break at the end of each file. Thus, the files where mixed
line break 
> flavour, which causes GNU recode to refuse the dos2unix
translation (no 
> --force switch there). I finally used zip/unzip to do the
conversion.

Well, sed 's/^M//' should be just OK instead of recode.
it won't complain. :)

anyway, I really wouldn't like SVN to try and outsmart me..
if I have 0x0d in my unix files, I probly put them there
for a reason, so my vote is a definite no for your wish if
it should be the default behavior.  If there is a
--be-smart-about-0x0d switch to do this,  then I have no
objection, though.
> 
cheers,
mitch
--
RADICS Peter (http://lbcons.net)