Replacing files forbidden because that would break *CVS* ?

[Matthias Andree]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 28.11.2013 08:02, schrieb Matthew Seaman:
> 
> Prompted by bsam, I'm attempting to re-connect the www/rt42 port with
> its history, buy 'svn rm'-ing the current www/rt42 contents, 'svn cp
> www/rt40 www/rt42' and then reapply the changes to the files.
> 
> Except I get this:
> 
> lucid-nonsense:~...ports/www/rt42:% /usr/ports/Tools/scripts/psvn commit
> ===> Do not replace files as this will break the CVS exporter: "."
> 
> Uh... do we still care about exporting to CVS?  I though CVS was long gone.
> 
> Any ideas on how I can achieve my aim of fixing the history for rt42
> gratefully received.

I agree we should lift limitations that were to assist CVS.

Can you "svn commit" before you svn cp to split the intended change in
two SVN revisions?  I seem to recall this was the canonical workaround
for the CVS exporter.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlKXDokACgkQvmGDOQUufZU6xgCfaOkIuOdjgcJhSGzmTwosj4TG
A1oAn1eb1pXilDWRDs5djhjJXQkHyjeQ
=FH0S
-----END PGP SIGNATURE-----