From now the sourcecode of DOSBox is stored in the SVN of sourceforge.
svn co https://dosbox.svn.sourceforge.net/svnroot/dosbox/dosbox/trunk dosbox
Water flows down the stream
How to ask questions the smart way!
Hurray! 😁
I hate svn 😀
I wondered what took you so long 😀
What, no git?
(sorry could not resist 😉
finally I can get "apt-get remove cvs" on my system, dosbox was the last project that I needed it for 😀
-Darkstar
Does anyone know why some files have unix eol style while others have dos eol?
since I'm on windows, I guess that svn should convert all files to dos eol style.
Could it be fixed with a command line switch?
Happens by times, usually we blame hal for that and qbix fixes it 😀 Any particular source file?
all source files, it seems. just a couple of files here and there are correct, i.e. vs project files.
Hm indeed, a windows checkout results in 0x0a endings and no eol svn property.
Maybe a problem of the cvs->svn conversion, anybody good with svn properties? 😀
Can't really help with the EOL style problems but I just wanted to point out that someone has created a git repository closely tracking the dosbox SVN, so if that's more convenient for anyone, here's the link:
http://github.com/Henne/dosbox-svn
-Darkstar
Hmm we should those line endings.
First time I heard of it. Guess visual studio doesn't have problems with the files ?
Water flows down the stream
How to ask questions the smart way!
Well since they're consistent, vs seems to "handle" them. Didn't check if they
are converted without notice, but on commit they'll be stored as 0x0a on the
server anyways i'd say.
Just want to avoid to have to change all files and re-upload them, maybe having
that eol svn property set for source files would be enough.
