[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Bern McCarty <Bern.McCarty_at_bentley.com>
Date: 2004-02-20 21:31:54 CET

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

I think leaving eol normalization off entirely is the right default for
cvs2svn and, in my observation, that's what it is doing now. Of course, it
would be good to have options to have it come out otherwise.

In my question I stipulated that EOL normalization was off. Do you mean to
say that there NO danger of corrupt binaries when EOL normalization is off
and svn:mime-type hasn't been set on your binary files appropriately? Why
wouldn't the scenario I described lead to a (unsafe) merge of a binary file?

I hope that enhancing cvs2svn to set svn:mime-type for -kb RCS files is a
high priority. Seems like everyone will need it. Lot of bang for the buck
there.

-Bern

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

Bern McCarty <Bern.McCarty@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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 20 21:32:10 2004

This is an archived mail posted to the Subversion Users mailing list.