> > 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.
I'm afraid that it may be a bit risky, but your post gave me an other idea.
What about if I dump the all repository and remove in the dump the
and then recreate it from the dump.
I didn't dare to do it directly in the repository because I didn't know
exactly the repository format and it seems that the properties are hashed or
something like that to keep the data consistency, but in the dump it should
be safe ! (shouldn't it ?)
Could a SVN developer confirm this please ?
Thank you very much
Received on Mon Oct 9 14:17:02 2006