On 10/9/06, Méresse Christophe <email@example.com> wrote:
> > > We have migrated 2 weeks ago some projects from CVS to SVN with the
> > > cvs2svn script. (about 13000 revisions) and I've noticed that the
> > > script has applied a svn:eol-style native to all our non binary
> > > files. I don't want this !
> > > [...]
> > Why don't you just redo the conversion, this time telling cvs2svn not
> > to apply svn:eol style properties? I think it has some option(s) for
> > controlling that. It only did it by default because you had the
> > corresponding CVS 'k' flags on those files, in fact.
> > -Karl
> Yes, there is an option (--no-default-eol), I will use it for the next migrations, but for this one the developers have made a lot of modifications during these two weeks so it would be a quite huge task to apply them again.
Actually, that may just not be the case: you could create a new
repository, which presumably will have the same number of revisions as
your original conversion. You can then dump the revisions which have
been committed the last weeks by running 'svnadmin dump
-r<last-rev-from-cvs2svn>'  to dump the modifications.
After that, you can load the modifications into the new repository
with 'svnadmin load' .
Your repository should then contain all changes except the eol
properties. All devs will need to checkout again though, because the
repository won't send eol style delete actions: it doesn't know the
local clients have it set.
Received on Mon Oct 9 11:57:56 2006