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

[Bern McCarty <Be...@bentley.com>]

I'm trying to understand whether this is an inconvenience or whether it is a
show stopper. 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? Would corruption only be possible when two clients
modified the same binary as in:

Clients 1 and 2 get working copies.  Client 1 modifies a binary working
copy.  Client 2 modifies the same binary in his working copy.  Client 1
checks in his change.  Client 2 does an update and instead of getting a
conflict may get a "merged" binary.  When client 2 checks in his change, he
checks in a corrupted file.

If you've left EOL normalization off completely, is this the only scenario
where the binaries could be corrupted by not identifying them as binary by
setting svn:mime-type appropriately?  Or is it worse than that....

-Bern

-----Original Message-----
From: haller@ableton.com [mailto:haller@ableton.com] 
Sent: Friday, February 20, 2004 2:55 AM
To: users@subversion.tigris.org
Subject: Re: How to get desired mime-types set for files during CVS to SVN
mig ration.

C. Michael Pilato <cm...@collab.net> wrote:

> Actually, that has me thinking.  If a file in CVS isn't binary, aren't 
> its newlines treated as "native"?  Might cvs2svn want to set that 
> property for non-binary files (of course, only after it learns to 
> recognize binary files)?

This may be dangerous, as Brane mentioned.  However, I need a solution for
this problem; this is one of the things that still prevents me from
switching to svn.  (I mean both of them: setting eol-style to native for
text files, and setting mime-type appropriately for binary files.)

I wonder if cvs2svn can be made to recognize my auto-props configuration?
(optionally perhaps?)  That would be ideal, I think.


--
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

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

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