Re: How to get desired mime-types set for files during CVS to SVN mig ration.

C. Michael Pilato wrote:

>Bern McCarty <Bern.McCarty@bentley.com> writes:
>
>
>
>>Does "svnadmin load" observe the autoprop configuration just like add and
>>import supposedly do? If not, how do you use cvs2svn.py and svnadmin load
>>to get your brand new repository off on the right foot with the desired
>>mime-types set on your files?
>>
>>
>
>No. 'svnadmin load' doesn't modify the data it is given, period.
>
>
>
>>Part of the reason I ask is because I see that the svn:mime-type property
>>can effect subversion operation regarding EOL handling.
>>
>>
>
>Actually, this is just a bug in cvs2svn. That program needs to notice
>the "b" flag in RCS files and set the svn:mime-type to
>application/x-octet-stream. This is part of Issue #1286.
>
>
Just application/octet-stream, I hope...

>Actually, that has me thinking. If a file in CVS isn't binary, aren't
>its newlines treated as "native"?
>
They are, at least by the Windows native clients.

> Might cvs2svn want to set that
>property for non-binary files (of course, only after it learns to
>recognize binary files)?
>
>
I'd hesitate to do that by default. If you use CVS exclusively on Unix,
it's quite easy to forget to set the binary flag, and not see a problem
(unless you try to cvs diff a binary file).

-- 
Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org