From owner-freebsd-ports@FreeBSD.ORG Thu Nov 28 09:36:25 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 011FFF18 for ; Thu, 28 Nov 2013 09:36:25 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 85F3E1148 for ; Thu, 28 Nov 2013 09:36:24 +0000 (UTC) Received: from mandree.no-ip.org ([78.48.141.48]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LezI3-1VHcQ20Cpr-00qhOt for ; Thu, 28 Nov 2013 10:36:17 +0100 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id D813523CE8F for ; Thu, 28 Nov 2013 10:36:15 +0100 (CET) Message-ID: <52970E8F.4060103@gmx.de> Date: Thu, 28 Nov 2013 10:36:15 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Replacing files forbidden because that would break *CVS* ? References: <5296EA8F.9050803@FreeBSD.org> In-Reply-To: <5296EA8F.9050803@FreeBSD.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:9xas4IzabMRksT+UP37F27uTWrV19Ce4bEEae+Z2NnKgJG18bp4 LSnI7f2nokbObKpqVHGgoUhAG7WN+rP8Zj1qze1eLaYlfyxVrbXeZOQYswQ7L0rKHQXvpF0 kzd0d6Ghe04+5FsM6NEcEWfO7CDxfzjk69pHjj9i7zFzvRP2FUt+s6LqWE1yPugfIekbdeP dO3qv5kVOnHvu2fkKBHbw== X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2013 09:36:25 -0000 -----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-----