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

[Stefan Haller <ha...@ableton.com>]

Bern McCarty <Be...@bentley.com> wrote:

> I'm trying to understand whether this is an inconvenience or whether it is a
> show stopper.

For me it's just an inconvenience, but it's inconvenient enough to keep
me from switching.  (Not the only reason though.)

> Can someone explain what actions could cause their binary
> files to become damaged because they were not properly identified as binary
> via svn:mime-type?

The possible damage Brane was talking about would happen when cvs2svn
would set eol-style=native on all files whose RCS file doesn't have the
"b" flag.

For me it's just inconvenient not to have my files labeled correctly.  I
could easily set all properties correctly after converting from CVS, but
then they would only apply from the current revision on, not for earlier
revisions.

A while ago someone suggested that you could run cvs2svn with
--dump-only, and then hack the dump file to insert the correct
properties for each file's first revision.  This might be possible, but
I have the feeling that cvs2svn should do this for me.

Are there any reasons why cvs2svn should *not* read my auto-props?
(Except that it may be some work to implement it?)


-- 
Stefan Haller
Ableton
http://www.ableton.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org